[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72TSJMTHFVC8FW2BGQ0NYD7":3,"skill-same:01M72TSJMTHFVC8FW2BGQ0NYD7":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},"01M72TSJMTHFVC8FW2BGQ0NYD7","ws-tdd-outline",null,"Phase 2 -- tree-level test design, examining intent and approach per test.","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.outline\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: ws-tdd-outline\ndescription: Phase 2 -- tree-level test design, examining intent and approach per test.\n---\n# ws.tdd.outline\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).\n\n## Purpose\n\nDesign individual test cases. For each idea: what it tests, what it does NOT test, exact AAA steps.\n\n**Cognitive mode: Tree, not forest.** Depth over breadth.\n\n## Prerequisites\n\n- Test ideas from `\u002Fws.tdd.idea` (Phase 1), reviewed and approved by human\n\n## Process\n\n### 1. Select Ideas\n\nAsk: \"Which ideas should I outline?\" (or confirm if human specified). If \"all\", proceed in logical groups.\n\n### 2. Write Outlines\n\nEnrich existing `todo`-marked stub with structured outline (docstring\u002Fcomments). Outline describes **scenario**, not mechanics -- survives as \"why\" layer above \"how.\"\n\nAAA comment failure modes:\n1. **Too mechanical** (restates code): `# Arrange: monkeypatch X to return Y` -- pseudo-code. Adds nothing.\n2. **Too absent**: loses scenario narrative. Reader sees *what* but not *why*.\n3. **Scenario narration** (sweet spot): *situation*, *domain-level action*, *expected truth*. Problem-domain language.\n\nGood-AAA test: helps understand story without reading code? Restates code -> delete. Deleting loses *why* -> keep. Take space for complex goals. Balance specificity\u002Ffreedom -- don't prescribe so tightly outline becomes pseudo-code.\n\n```python\n# BAD -- too mechanical (restates code):\n# Arrange: create a path \"\u002Fnonexistent\u002Fpath\u002Fdata.xml\"\n# Act: call OutputMapper(bad_path)\n# Assert: raises FileNotFoundError\n\n# BAD -- too absent:\n# (no comments, just docstring)\n\n# GOOD -- scenario narration:\n# Arrange: a path that cannot exist on any filesystem\n# Act: construct the mapper -- failure must happen here, not later\n# Assert: FileNotFoundError at construction time, not at first use\n```\n\n```python\n@pytest.mark.todo\ndef test_output_mapper_throws_on_missing_file():\n    \"\"\"Verify fail-fast on missing file -- must fail at construction,\n    not silently at first use.\n\n    Boundaries: Only tests missing file; malformed content is separate.\n                Does not test error message wording.\n    \"\"\"\n    # Arrange: a path that cannot exist on any filesystem\n    # Act: construct the mapper -- failure must happen here, not later\n    # Assert: FileNotFoundError at construction time, not at first use\n    pytest.skip(\"TODO: Outlined, not yet implemented\")\n```\n\n```cpp\nTEST_CASE(\"OutputMapper throws on missing file\", \"[.][todo]\") {\n    \u002F\u002F Goal: Verify fail-fast on missing file -- must fail at construction,\n    \u002F\u002F       not silently at first use\n    \u002F\u002F Boundaries: Only tests missing file; malformed content is separate.\n    \u002F\u002F             Does not test error message wording.\n    \u002F\u002F Arrange: a path that cannot exist on any filesystem\n    \u002F\u002F Act: construct the mapper -- failure must happen here, not later\n    \u002F\u002F Assert: FileNotFoundError at construction time, not at first use\n    SKIP(\"TODO: Outlined, not yet implemented\");\n}\n```\n\n**Batch size: the Outline rate limit in `ws.tdd._meta`.** Align batches to topic groups — neither fragment a group to hit the target exactly, nor batch everything because each topic is \"whole.\" See also \"Batch Processing Flow\" there.\n\n### 3. Challenge Assertion Precision\n\nFor each outline: Deep enough? (\"not empty\" vs. \"correct count\" vs. \"correct content\") \u002F Exact expected values? (count==3, not count>0) \u002F Right thing? (behavior vs. implementation detail) \u002F False positive? (passes but code wrong) \u002F **Clearing path**: sets mutable state -> companion test verifies **cleared** state? Every \"set\" needs tested \"clear.\" Untested = latent bug (state accumulates across cycles).\n\n## Output\n\nEnriched `todo`-marked stubs with Goal\u002FBoundaries\u002FAAA. Tests remain skip-marked.\n\n## Behaviors\n\n- Primary activity = outlining, not generating new ideas\n- New idea discovered: record placeholder, flag to human. Don't silently expand scope; don't lose discoveries.\n- State what test does NOT cover (as important as what it does)\n- \"Checks output is correct\" = wish, not outline\n- Idea is multiple tests -> split, explain why\n- **Shared setup**: Common Arrange patterns -> note for shared fixture during red\n- **Outline desired behavior, not current**: Code wrong -> outline what it *should* do. Test fails red, green fixes. Never fix production before outline exists.\n\n## Anti-Patterns\n\n- Writing executable code (Phase 3)\n- Mechanical AAA restating code \u002F absent AAA leaving only docstring \u002F vague AAA (\"output is correct\")\n- Fragmenting topic group to hit the target exactly \u002F batching all remaining because each is \"whole\"\n- Drifting to forest-level -- flag: \"Should we return to `\u002Fws.tdd.idea`?\"\n\n## Gate\n\nPresent outlines. Wait for review before `\u002Fws.tdd.red`. Human may revise assertions, adjust boundaries, question depth.\n","# ws.tdd.outline\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).\n\n## Purpose\n\nDesign individual test cases. For each idea: what it tests, what it does NOT test, exact AAA steps.\n\n**Cognitive mode: Tree, not forest.** Depth over breadth.\n\n## Prerequisites\n\n- Test ideas from `\u002Fws.tdd.idea` (Phase 1), reviewed and approved by human\n\n## Process\n\n### 1. Select Ideas\n\nAsk: \"Which ideas should I outline?\" (or confirm if human specified). If \"all\", proceed in logical groups.\n\n### 2. Write Outlines\n\nEnrich existing `todo`-marked stub with structured outline (docstring\u002Fcomments). Outline describes **scenario**, not mechanics -- survives as \"why\" layer above \"how.\"\n\nAAA comment failure modes:\n1. **Too mechanical** (restates code): `# Arrange: monkeypatch X to return Y` -- pseudo-code. Adds nothing.\n2. **Too absent**: loses scenario narrative. Reader sees *what* but not *why*.\n3. **Scenario narration** (sweet spot): *situation*, *domain-level action*, *expected truth*. Problem-domain language.\n\nGood-AAA test: helps understand story without reading code? Restates code -> delete. Deleting loses *why* -> keep. Take space for complex goals. Balance specificity\u002Ffreedom -- don't prescribe so tightly outline becomes pseudo-code.\n\n```python\n# BAD -- too mechanical (restates code):\n# Arrange: create a path \"\u002Fnonexistent\u002Fpath\u002Fdata.xml\"\n# Act: call OutputMapper(bad_path)\n# Assert: raises FileNotFoundError\n\n# BAD -- too absent:\n# (no comments, just docstring)\n\n# GOOD -- scenario narration:\n# Arrange: a path that cannot exist on any filesystem\n# Act: construct the mapper -- failure must happen here, not later\n# Assert: FileNotFoundError at construction time, not at first use\n```\n\n```python\n@pytest.mark.todo\ndef test_output_mapper_throws_on_missing_file():\n    \"\"\"Verify fail-fast on missing file -- must fail at construction,\n    not silently at first use.\n\n    Boundaries: Only tests missing file; malformed content is separate.\n                Does not test error message wording.\n    \"\"\"\n    # Arrange: a path that cannot exist on any filesystem\n    # Act: construct the mapper -- failure must happen here, not later\n    # Assert: FileNotFoundError at construction time, not at first use\n    pytest.skip(\"TODO: Outlined, not yet implemented\")\n```\n\n```cpp\nTEST_CASE(\"OutputMapper throws on missing file\", \"[.][todo]\") {\n    \u002F\u002F Goal: Verify fail-fast on missing file -- must fail at construction,\n    \u002F\u002F       not silently at first use\n    \u002F\u002F Boundaries: Only tests missing file; malformed content is separate.\n    \u002F\u002F             Does not test error message wording.\n    \u002F\u002F Arrange: a path that cannot exist on any filesystem\n    \u002F\u002F Act: construct the mapper -- failure must happen here, not later\n    \u002F\u002F Assert: FileNotFoundError at construction time, not at first use\n    SKIP(\"TODO: Outlined, not yet implemented\");\n}\n```\n\n**Batch size: the Outline rate limit in `ws.tdd._meta`.** Align batches to topic groups — neither fragment a group to hit the target exactly, nor batch everything because each topic is \"whole.\" See also \"Batch Processing Flow\" there.\n\n### 3. Challenge Assertion Precision\n\nFor each outline: Deep enough? (\"not empty\" vs. \"correct count\" vs. \"correct content\") \u002F Exact expected values? (count==3, not count>0) \u002F Right thing? (behavior vs. implementation detail) \u002F False positive? (passes but code wrong) \u002F **Clearing path**: sets mutable state -> companion test verifies **cleared** state? Every \"set\" needs tested \"clear.\" Untested = latent bug (state accumulates across cycles).\n\n## Output\n\nEnriched `todo`-marked stubs with Goal\u002FBoundaries\u002FAAA. Tests remain skip-marked.\n\n## Behaviors\n\n- Primary activity = outlining, not generating new ideas\n- New idea discovered: record placeholder, flag to human. Don't silently expand scope; don't lose discoveries.\n- State what test does NOT cover (as important as what it does)\n- \"Checks output is correct\" = wish, not outline\n- Idea is multiple tests -> split, explain why\n- **Shared setup**: Common Arrange patterns -> note for shared fixture during red\n- **Outline desired behavior, not current**: Code wrong -> outline what it *should* do. Test fails red, green fixes. Never fix production before outline exists.\n\n## Anti-Patterns\n\n- Writing executable code (Phase 3)\n- Mechanical AAA restating code \u002F absent AAA leaving only docstring \u002F vague AAA (\"output is correct\")\n- Fragmenting topic group to hit the target exactly \u002F batching all remaining because each is \"whole\"\n- Drifting to forest-level -- flag: \"Should we return to `\u002Fws.tdd.idea`?\"\n\n## Gate\n\nPresent outlines. Wait for review before `\u002Fws.tdd.red`. Human may revise assertions, adjust boundaries, question depth.\n",{"name":5,"description":7},"main","1ad262fc695612ff484ee364ff66ab5298bdda58","skills\u002Fws.tdd.outline",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-outline",{"tool":36,"command":37},"bunx","bunx skills add vempio\u002FWhittleSpec --skill ws-tdd-outline",{"tool":39,"command":40},"pnpm","pnpm dlx skills add vempio\u002FWhittleSpec --skill ws-tdd-outline","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvempio\u002FWhittleSpec\u002Fblob\u002Fmain\u002Fskills\u002Fws.tdd.outline\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},"01M72TSN33MN2J0CW29MBY4WC4","ws-tdd-red","Phase 3 -- implement failing tests, validating assertion quality and depth.","https:\u002F\u002Fgithub.com\u002Fvempio\u002FWhittleSpec\u002Fblob\u002Fmain\u002Fskills\u002Fws.tdd.red\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",[],[]]