[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72TSN33MN2J0CW29MBY4WC4":3,"skill-same:01M72TSN33MN2J0CW29MBY4WC4":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M72TSN33MN2J0CW29MBY4WC4","ws-tdd-red",null,"Phase 3 -- implement failing tests, validating assertion quality and depth.","vempio\u002FWhittleSpec","vempio","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F226084226?v=4","01M72TQW11B57V5ZE8MQPKJ5QY","01M72TQW22F5C4SJ317ETCWHFW",4,"MIT","https:\u002F\u002Fgithub.com\u002Fvempio\u002FWhittleSpec\u002Fblob\u002Fmain\u002Fskills\u002Fws.tdd.red\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: ws-tdd-red\ndescription: Phase 3 -- implement failing tests, validating assertion quality and depth.\n---\n# ws.tdd.red\n\nLoad shared context: `ws.tdd._meta\u002FSKILL.md` — the sibling skill in the same skills directory this skill loaded from (resolves under any clone name, install location, or skills-root override). Also read `ws.tdd._meta\u002Fvisibility-patterns.md` and `ws.tdd._meta\u002Ftraceability.md`.\n\n## Purpose\n\nTurn outlines into executable test code. Not \"does test run\" but \"does test assert right thing at right depth?\" **Cognitive mode: Validation of validations.** Scrutinize every assertion -- checking what matters? deeply enough? subtly wrong impl still pass?\n\n**Prerequisites**: Test outlines from `\u002Fws.tdd.outline` (Phase 2), reviewed and approved by human.\n\n## Process\n\n### 1. Select Outlines\nAsk: \"Which outlines to implement?\" (or confirm if human specified). **Max 3 per turn.**\n**BDD awareness**: `.feature` files have `@todo` scenarios for this feature -> \"Note: N BDD scenarios still `@todo` -- should route through `\u002Fws.bdd.outline` -> `\u002Fws.bdd.red`.\" Not blocker, surfaces gap.\n\n### 2. Implement\nRemove `todo` marker and skip, replace with real assertions. **Outline comments must survive** -- \"why\u002Fwhat\" above \"how.\" Comments follow AAA structure, explain intent not mechanics. Comment redundant with code -> outline at wrong abstraction -- raise with human, don't silently drop.\n\n```python\n# Goal: Verify fail-fast behavior when input file doesn't exist --\n#       missing files must be caught at construction time, not at first use\n# Boundaries: Only tests missing file; malformed content is separate.\n#             Does not test the error message content.\ndef test_output_mapper_throws_on_missing_file():\n    # Arrange: use a path that cannot exist\n    bad_path = \"\u002Fnonexistent\u002Fpath\u002Fdata.xml\"\n\n    # Act + Assert: construction itself must fail, not a later method call\n    with pytest.raises(FileNotFoundError, match=bad_path):\n        OutputMapper(bad_path)\n```\n\n```cpp\n\u002F\u002F Goal: Verify fail-fast behavior when input file doesn't exist --\n\u002F\u002F       missing files must be caught at construction time, not at first use\n\u002F\u002F Boundaries: Only tests missing file; malformed content is separate.\n\u002F\u002F             Does not test the error message content.\nTEST_CASE(\"OutputMapper throws on missing file\", \"[error]\") {\n    \u002F\u002F Arrange: use a path that cannot exist\n    auto bad_path = \"\u002Fnonexistent\u002Fpath\u002Fdata.xml\";\n\n    \u002F\u002F Act + Assert: construction itself must fail, not a later method call\n    REQUIRE_THROWS_AS(OutputMapper(bad_path), std::runtime_error);\n    REQUIRE_THROWS_WITH(OutputMapper(bad_path), Catch::Contains(bad_path));\n}\n```\n\n### 3. Run Test Suite\nRun **entire** suite. New tests **should fail** -- passing immediately -> investigate: vacuously passing (success theater)? existing code handles case (acceptable but steps too large)? Existing tests must still pass.\n\n### 4. Review Failures\nEach: **right reason** (missing impl, not test bug)? \u002F informative message? \u002F assertion depth matches outline intent?\n\n### 5. Coverage Report (when SDD context available)\n\"X of Y acceptance criteria have executable tests. Outline only: [list]. Uncovered: [list].\"\n\n## Output\nExecutable, failing test code. Suite has been run.\n\n## Behaviors\n- Every assertion = design decision: \"`assert len(result) == 3` enough, or also check `result[0].name == 'expected'`?\"\n- **Exact values, not defensive ranges.** `== 1` not `>= 1`. `== \"success\"` not `is not None`. Weak assertions worse than no test. See \"Assertion Precision\" in `ws.tdd._meta`.\n- \"Verify content\" = verify content, not presence\u002Fcount. Under-specified outline: note it, don't silently decide.\n- Test independence: no test depends on another's execution\u002Fstate. **Extract shared setup**: fixtures\u002Fhelpers for common setup, vary only what differs.\n\n## Anti-Patterns\n**Success theater** (`assert True` \u002F unfailable assertions) \u002F **writing production code** (Phase 4) \u002F **skipping new tests** (wrote it = runs) \u002F **weakening assertions** (\"check content\" -> \"check not empty\") \u002F **exceeding 3 per turn** \u002F **catching exceptions** to prevent failure.\n\n### Assertion Precision Checkpoint\nAfter each batch, before gate: **\"Would subtly wrong impl still pass?\"** `> 0`\u002F`is not None` where exact value known -> `== exact_value` \u002F presence not content -> add content \u002F type not value -> add value \u002F one field ignoring related -> add missing. Fix before gate.\n\n## Gate\nPresent tests + failure output. Wait for confirmation: (1) fail for right reasons (2) assertion depth correct (3) ready for `\u002Fws.tdd.green`.\n\n## After Green\nReturn for next batch (max 3\u002Fturn). All outlines done -> back to `\u002Fws.tdd.outline`. See \"Batch Processing Flow\" in `ws.tdd._meta`.\n","# ws.tdd.red\n\nLoad shared context: `ws.tdd._meta\u002FSKILL.md` — the sibling skill in the same skills directory this skill loaded from (resolves under any clone name, install location, or skills-root override). Also read `ws.tdd._meta\u002Fvisibility-patterns.md` and `ws.tdd._meta\u002Ftraceability.md`.\n\n## Purpose\n\nTurn outlines into executable test code. Not \"does test run\" but \"does test assert right thing at right depth?\" **Cognitive mode: Validation of validations.** Scrutinize every assertion -- checking what matters? deeply enough? subtly wrong impl still pass?\n\n**Prerequisites**: Test outlines from `\u002Fws.tdd.outline` (Phase 2), reviewed and approved by human.\n\n## Process\n\n### 1. Select Outlines\nAsk: \"Which outlines to implement?\" (or confirm if human specified). **Max 3 per turn.**\n**BDD awareness**: `.feature` files have `@todo` scenarios for this feature -> \"Note: N BDD scenarios still `@todo` -- should route through `\u002Fws.bdd.outline` -> `\u002Fws.bdd.red`.\" Not blocker, surfaces gap.\n\n### 2. Implement\nRemove `todo` marker and skip, replace with real assertions. **Outline comments must survive** -- \"why\u002Fwhat\" above \"how.\" Comments follow AAA structure, explain intent not mechanics. Comment redundant with code -> outline at wrong abstraction -- raise with human, don't silently drop.\n\n```python\n# Goal: Verify fail-fast behavior when input file doesn't exist --\n#       missing files must be caught at construction time, not at first use\n# Boundaries: Only tests missing file; malformed content is separate.\n#             Does not test the error message content.\ndef test_output_mapper_throws_on_missing_file():\n    # Arrange: use a path that cannot exist\n    bad_path = \"\u002Fnonexistent\u002Fpath\u002Fdata.xml\"\n\n    # Act + Assert: construction itself must fail, not a later method call\n    with pytest.raises(FileNotFoundError, match=bad_path):\n        OutputMapper(bad_path)\n```\n\n```cpp\n\u002F\u002F Goal: Verify fail-fast behavior when input file doesn't exist --\n\u002F\u002F       missing files must be caught at construction time, not at first use\n\u002F\u002F Boundaries: Only tests missing file; malformed content is separate.\n\u002F\u002F             Does not test the error message content.\nTEST_CASE(\"OutputMapper throws on missing file\", \"[error]\") {\n    \u002F\u002F Arrange: use a path that cannot exist\n    auto bad_path = \"\u002Fnonexistent\u002Fpath\u002Fdata.xml\";\n\n    \u002F\u002F Act + Assert: construction itself must fail, not a later method call\n    REQUIRE_THROWS_AS(OutputMapper(bad_path), std::runtime_error);\n    REQUIRE_THROWS_WITH(OutputMapper(bad_path), Catch::Contains(bad_path));\n}\n```\n\n### 3. Run Test Suite\nRun **entire** suite. New tests **should fail** -- passing immediately -> investigate: vacuously passing (success theater)? existing code handles case (acceptable but steps too large)? Existing tests must still pass.\n\n### 4. Review Failures\nEach: **right reason** (missing impl, not test bug)? \u002F informative message? \u002F assertion depth matches outline intent?\n\n### 5. Coverage Report (when SDD context available)\n\"X of Y acceptance criteria have executable tests. Outline only: [list]. Uncovered: [list].\"\n\n## Output\nExecutable, failing test code. Suite has been run.\n\n## Behaviors\n- Every assertion = design decision: \"`assert len(result) == 3` enough, or also check `result[0].name == 'expected'`?\"\n- **Exact values, not defensive ranges.** `== 1` not `>= 1`. `== \"success\"` not `is not None`. Weak assertions worse than no test. See \"Assertion Precision\" in `ws.tdd._meta`.\n- \"Verify content\" = verify content, not presence\u002Fcount. Under-specified outline: note it, don't silently decide.\n- Test independence: no test depends on another's execution\u002Fstate. **Extract shared setup**: fixtures\u002Fhelpers for common setup, vary only what differs.\n\n## Anti-Patterns\n**Success theater** (`assert True` \u002F unfailable assertions) \u002F **writing production code** (Phase 4) \u002F **skipping new tests** (wrote it = runs) \u002F **weakening assertions** (\"check content\" -> \"check not empty\") \u002F **exceeding 3 per turn** \u002F **catching exceptions** to prevent failure.\n\n### Assertion Precision Checkpoint\nAfter each batch, before gate: **\"Would subtly wrong impl still pass?\"** `> 0`\u002F`is not None` where exact value known -> `== exact_value` \u002F presence not content -> add content \u002F type not value -> add value \u002F one field ignoring related -> add missing. Fix before gate.\n\n## Gate\nPresent tests + failure output. Wait for confirmation: (1) fail for right reasons (2) assertion depth correct (3) ready for `\u002Fws.tdd.green`.\n\n## After Green\nReturn for next batch (max 3\u002Fturn). All outlines done -> back to `\u002Fws.tdd.outline`. See \"Batch Processing Flow\" in `ws.tdd._meta`.\n",{"name":5,"description":7},"main","1ad262fc695612ff484ee364ff66ab5298bdda58","skills\u002Fws.tdd.red",0,"https:\u002F\u002Fgithub.com\u002Fvempio\u002FWhittleSpec","https:\u002F\u002Fgithub.com\u002Fvempio","2026-10-06 16:08:48",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add vempio\u002FWhittleSpec --skill ws-tdd-red",{"tool":36,"command":37},"bunx","bunx skills add vempio\u002FWhittleSpec --skill ws-tdd-red",{"tool":39,"command":40},"pnpm","pnpm dlx skills add vempio\u002FWhittleSpec --skill ws-tdd-red","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvempio\u002FWhittleSpec\u002Fblob\u002Fmain\u002Fskills\u002Fws.tdd.red\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M72TSQYBBJ3FG1MSMB9B33SZ","ws-tdd-review","Audit existing test code for quality, depth, and adherence to TDD principles.","https:\u002F\u002Fgithub.com\u002Fvempio\u002FWhittleSpec\u002Fblob\u002Fmain\u002Fskills\u002Fws.tdd.review\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M72TSJMTHFVC8FW2BGQ0NYD7","ws-tdd-outline","Phase 2 -- tree-level test design, examining intent and approach per test.","https:\u002F\u002Fgithub.com\u002Fvempio\u002FWhittleSpec\u002Fblob\u002Fmain\u002Fskills\u002Fws.tdd.outline\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M72TSFPHD749CY9KRV66T0RH","ws-tdd-idea","Phase 1 -- forest-level test case discovery, mapping the full problem space.","https:\u002F\u002Fgithub.com\u002Fvempio\u002FWhittleSpec\u002Fblob\u002Fmain\u002Fskills\u002Fws.tdd.idea\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M72TSD53VT09VF3EG67KA68E","ws-tdd-green","Phase 4 -- write minimal production code to make failing tests pass.","https:\u002F\u002Fgithub.com\u002Fvempio\u002FWhittleSpec\u002Fblob\u002Fmain\u002Fskills\u002Fws.tdd.green\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M72TS9TXQ9RHYF3VBGR87BF6","ws-tdd-meta","TDD shared context -- phased protocol, quality standards, and standing instructions for all TDD skills.","https:\u002F\u002Fgithub.com\u002Fvempio\u002FWhittleSpec\u002Fblob\u002Fmain\u002Fskills\u002Fws.tdd._meta\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M72TS76RJ3K1HNGQXJ2S09HT","ws-sweep","Completeness sweep -- exhaustively verify nothing was missed after a change.","https:\u002F\u002Fgithub.com\u002Fvempio\u002FWhittleSpec\u002Fblob\u002Fmain\u002Fskills\u002Fws.sweep\u002FSKILL.md",[],[]]