[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72TRX8N3GFBZ74WZCD4KWH4":3,"skill-same:01M72TRX8N3GFBZ74WZCD4KWH4":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},"01M72TRX8N3GFBZ74WZCD4KWH4","ws-refine",null,"Mid-flight adjustment — incorporate learning, restructure tasks, or defer. Orchestrates review on affected artifacts.","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.refine\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: ws-refine\ndescription: Mid-flight adjustment — incorporate learning, restructure tasks, or defer. Orchestrates review on affected artifacts.\n---\n# ws.refine\n\nLoad shared context: `ws._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 load: `ws._meta\u002Fshaping.md`, `ws._meta\u002Flifecycle.md`, `ws._meta\u002Fparallel-work.md`, `ws._meta\u002Fissue-tracking.md`.\n\n## Purpose\n\nHandle discoveries during specification or implementation. Two paths: (1) **Protect focus** -- capture distractions, continue current work. (2) **Incorporate learning** -- update specs when new info matters now. Both end same way: back to what you were doing.\n\n## When to Use\n\nDiscovery that might change specs \u002F implementation revealed gap or contradiction \u002F new requirement emerged mid-flight \u002F assumption proved wrong. Also invoked passively: if AI detects drift during work, suggest `\u002Fws.refine`.\n\n## Process\n\n### 1. Articulate Discovery\n\nState: \"What did we learn?\" \u002F \"Where from?\" (implementation, conversation, external input)\n\n### 2. Assess Relevance\n\n\"Does this change what we're currently doing?\" Check task file(s) for `[~]` markers. If affected tasks are in-flight (another session), warn: \"Task N is in-flight -- this change may cause conflicts with parallel work.\"\n\n```\nDiscovery -> CURRENT work or FUTURE?\n  CURRENT -> Incorporate (Step 3a)\n  FUTURE  -> Capture for later (Step 3b)\n```\n\n### 3a. Incorporate (Current Work)\n\n1. **Identify affected levels** -- Requirements \u002F plan \u002F tasks change? Does it ripple?\n2. **Assess scope impact** -- Minor tweak? Restructure? Scope reduction (good!) \u002F expansion (be wary)?\n3. **Propose specific changes** -- Quote current, show proposed, explain why.\n4. **Update artifacts** with user approval.\n5. **Review affected artifacts** -- Run `\u002Fws.review` (composable mode) on changed artifacts. Catches second-order problems: fix for one gap may open another.\n6. **Restructure task list** if discovery affects tasks:\n   - **Stable task numbering (HARD RULE)**: Never renumber existing tasks. Completed `[x]` and in-flight `[~]` keep their numbers. New tasks use letter suffixes: between 19 and 20, insert 19a (then 19b, 19c).\n   - **Task identity preservation**: If scope movement changes task's goal beyond recognition, mark obsolete (`[OBSOLETE -- replaced by 19a]`) and create new task. Task number is stable reference (commit messages, the tracker, parallel sessions).\n   - **Scope movement within reason**: Subtasks\u002FACs may move between tasks, but each must remain closed, verifiable, valuable increment. Walking skeleton and vertical slice compliance from `\u002Fws.3-tasks` still apply.\n   - **Review restructured list**: Verify vertical slice compliance. Each task must leave project testable, wire into production, advance BDD\u002Fdocs where applicable.\n   - **Warn about in-flight interference**: If restructuring affects `[~]` task, warn explicitly about parallel session conflicts.\n7. **Check work-ledger alignment** (resolve `ws-binding get work-ledger`; see `ws._meta\u002FSKILL.md` § Work-ledger binding) -- tracker bound: scope change affect the linked issue? (Summary mismatch, new slice, ACs shifted.) Update the issue or create a new one? If no reference yet, does this tip work into \"committed\" territory? `local`: the task\u002Fspec files are the record — keep them current, no external issue.\n\n### 3b. Defer (Future Work)\n\n**MANDATORY: Every deferral persisted to durable artifact.** Conversation-only deferral = failed refinement.\n\n1. **Persist** -- choose destination:\n   - **a)** Active SDD workstream (task file present): Append to Backlog section.\n   - **b)** No task file, relates to existing spec\u002Fworkflow: Append \"Future Work\"\u002F\"Backlog\" section.\n   - **c)** No task file, no related spec: record it in the work ledger immediately — a tracked issue if a tracker is bound, else a `local` task\u002Fspec entry.\n   - **d)** Large enough for own workstream (spec kernel): Create `specs\u002F\u003Cworkflow-name>\u002Fseed.md` with full context. If the item came from `specs\u002F_ideas.md`, remove it there; the seed becomes source of truth. Do NOT create a tracker epic yet.\n   - **e)** Belongs to a domain the project captures elsewhere (process\u002Fworkflow observation, research note): resolve `ws-binding get discovery-capture` and route by the recorded rule. Unbound → no such destination exists here; use (a)-(d). See `ws._meta\u002Flifecycle.md` § Discovery-capture binding.\n   - For all paths: **check tracker implications** (comment on current issue? own issue needed?).\n   - Write enough context for self-explanatory reading weeks later.\n\n```markdown\n## Backlog (Deferred)\n- [Discovery]: [Description -- enough to act on cold]\n  - Source: [task, conversation, implementation detail]\n  - Context: [What were we doing? Connection?]\n  - Why deferred: [Not blocking because...]\n  - Impact if forgotten: [What breaks\u002Fdegrades?]\n  - Revisit when: [Concrete condition, not \"later\"]\n  - Persisted to: [File path, tracker ID, or both]\n```\n\n2. **Verify persistence**: Confirm \"Persisted to [location].\" Can't point to file or ticket = not finished.\n3. **Don't chase** -- return to current work.\n4. **Note**: \"Captured [X] in [location]. Returning to [current task].\"\n\n> **Lifecycle**: Deferred items revisited during `\u002Fws.9-retro` (step 5: Future Seeding). Between retros, `\u002Fws.status` surfaces backlog health.\n\n### 4. Resume\n\n\"Discovery handled. Back to [what we were doing].\" \u002F \"Returning to Task N...\"\n\n## Output\n\n**If incorporated**:\n```markdown\n## Refinement Applied\n**Discovery**: [What we learned]\n**Affected**: [requirements.md \u002F umbrella-requirements.md \u002F plan.md \u002F umbrella-plan.md \u002F task file]\n**Changes made**: [File]: [Summary]\n**Review findings**: [Summary or \"no new issues\"]\n**Task restructuring**: [Changes or \"none needed\"]\n**Resuming**: [Current task\u002Factivity]\n```\n\n**If deferred**:\n```markdown\n## Refinement Deferred\n**Discovery**: [What we learned]\n**Persisted to**: [Location]\n**Context**: [What we were doing, why this came up]\n**Reason**: [Not blocking because...]\n**Impact if forgotten**: [What breaks\u002Fdegrades]\n**Revisit when**: [Concrete condition]\n**Resuming**: [Current task\u002Factivity]\n```\n\n## Anti-Patterns\n\n- **Discussing without persisting** -- most common failure. Not in durable artifact = didn't happen.\n- Chasing every discovery immediately (scope creep)\n- Ignoring discoveries that should change plan (drift)\n- Changes without noting them (invisible drift)\n- Deferring everything (never learning)\n- Large rewrites without user approval\n","# ws.refine\n\nLoad shared context: `ws._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 load: `ws._meta\u002Fshaping.md`, `ws._meta\u002Flifecycle.md`, `ws._meta\u002Fparallel-work.md`, `ws._meta\u002Fissue-tracking.md`.\n\n## Purpose\n\nHandle discoveries during specification or implementation. Two paths: (1) **Protect focus** -- capture distractions, continue current work. (2) **Incorporate learning** -- update specs when new info matters now. Both end same way: back to what you were doing.\n\n## When to Use\n\nDiscovery that might change specs \u002F implementation revealed gap or contradiction \u002F new requirement emerged mid-flight \u002F assumption proved wrong. Also invoked passively: if AI detects drift during work, suggest `\u002Fws.refine`.\n\n## Process\n\n### 1. Articulate Discovery\n\nState: \"What did we learn?\" \u002F \"Where from?\" (implementation, conversation, external input)\n\n### 2. Assess Relevance\n\n\"Does this change what we're currently doing?\" Check task file(s) for `[~]` markers. If affected tasks are in-flight (another session), warn: \"Task N is in-flight -- this change may cause conflicts with parallel work.\"\n\n```\nDiscovery -> CURRENT work or FUTURE?\n  CURRENT -> Incorporate (Step 3a)\n  FUTURE  -> Capture for later (Step 3b)\n```\n\n### 3a. Incorporate (Current Work)\n\n1. **Identify affected levels** -- Requirements \u002F plan \u002F tasks change? Does it ripple?\n2. **Assess scope impact** -- Minor tweak? Restructure? Scope reduction (good!) \u002F expansion (be wary)?\n3. **Propose specific changes** -- Quote current, show proposed, explain why.\n4. **Update artifacts** with user approval.\n5. **Review affected artifacts** -- Run `\u002Fws.review` (composable mode) on changed artifacts. Catches second-order problems: fix for one gap may open another.\n6. **Restructure task list** if discovery affects tasks:\n   - **Stable task numbering (HARD RULE)**: Never renumber existing tasks. Completed `[x]` and in-flight `[~]` keep their numbers. New tasks use letter suffixes: between 19 and 20, insert 19a (then 19b, 19c).\n   - **Task identity preservation**: If scope movement changes task's goal beyond recognition, mark obsolete (`[OBSOLETE -- replaced by 19a]`) and create new task. Task number is stable reference (commit messages, the tracker, parallel sessions).\n   - **Scope movement within reason**: Subtasks\u002FACs may move between tasks, but each must remain closed, verifiable, valuable increment. Walking skeleton and vertical slice compliance from `\u002Fws.3-tasks` still apply.\n   - **Review restructured list**: Verify vertical slice compliance. Each task must leave project testable, wire into production, advance BDD\u002Fdocs where applicable.\n   - **Warn about in-flight interference**: If restructuring affects `[~]` task, warn explicitly about parallel session conflicts.\n7. **Check work-ledger alignment** (resolve `ws-binding get work-ledger`; see `ws._meta\u002FSKILL.md` § Work-ledger binding) -- tracker bound: scope change affect the linked issue? (Summary mismatch, new slice, ACs shifted.) Update the issue or create a new one? If no reference yet, does this tip work into \"committed\" territory? `local`: the task\u002Fspec files are the record — keep them current, no external issue.\n\n### 3b. Defer (Future Work)\n\n**MANDATORY: Every deferral persisted to durable artifact.** Conversation-only deferral = failed refinement.\n\n1. **Persist** -- choose destination:\n   - **a)** Active SDD workstream (task file present): Append to Backlog section.\n   - **b)** No task file, relates to existing spec\u002Fworkflow: Append \"Future Work\"\u002F\"Backlog\" section.\n   - **c)** No task file, no related spec: record it in the work ledger immediately — a tracked issue if a tracker is bound, else a `local` task\u002Fspec entry.\n   - **d)** Large enough for own workstream (spec kernel): Create `specs\u002F\u003Cworkflow-name>\u002Fseed.md` with full context. If the item came from `specs\u002F_ideas.md`, remove it there; the seed becomes source of truth. Do NOT create a tracker epic yet.\n   - **e)** Belongs to a domain the project captures elsewhere (process\u002Fworkflow observation, research note): resolve `ws-binding get discovery-capture` and route by the recorded rule. Unbound → no such destination exists here; use (a)-(d). See `ws._meta\u002Flifecycle.md` § Discovery-capture binding.\n   - For all paths: **check tracker implications** (comment on current issue? own issue needed?).\n   - Write enough context for self-explanatory reading weeks later.\n\n```markdown\n## Backlog (Deferred)\n- [Discovery]: [Description -- enough to act on cold]\n  - Source: [task, conversation, implementation detail]\n  - Context: [What were we doing? Connection?]\n  - Why deferred: [Not blocking because...]\n  - Impact if forgotten: [What breaks\u002Fdegrades?]\n  - Revisit when: [Concrete condition, not \"later\"]\n  - Persisted to: [File path, tracker ID, or both]\n```\n\n2. **Verify persistence**: Confirm \"Persisted to [location].\" Can't point to file or ticket = not finished.\n3. **Don't chase** -- return to current work.\n4. **Note**: \"Captured [X] in [location]. Returning to [current task].\"\n\n> **Lifecycle**: Deferred items revisited during `\u002Fws.9-retro` (step 5: Future Seeding). Between retros, `\u002Fws.status` surfaces backlog health.\n\n### 4. Resume\n\n\"Discovery handled. Back to [what we were doing].\" \u002F \"Returning to Task N...\"\n\n## Output\n\n**If incorporated**:\n```markdown\n## Refinement Applied\n**Discovery**: [What we learned]\n**Affected**: [requirements.md \u002F umbrella-requirements.md \u002F plan.md \u002F umbrella-plan.md \u002F task file]\n**Changes made**: [File]: [Summary]\n**Review findings**: [Summary or \"no new issues\"]\n**Task restructuring**: [Changes or \"none needed\"]\n**Resuming**: [Current task\u002Factivity]\n```\n\n**If deferred**:\n```markdown\n## Refinement Deferred\n**Discovery**: [What we learned]\n**Persisted to**: [Location]\n**Context**: [What we were doing, why this came up]\n**Reason**: [Not blocking because...]\n**Impact if forgotten**: [What breaks\u002Fdegrades]\n**Revisit when**: [Concrete condition]\n**Resuming**: [Current task\u002Factivity]\n```\n\n## Anti-Patterns\n\n- **Discussing without persisting** -- most common failure. Not in durable artifact = didn't happen.\n- Chasing every discovery immediately (scope creep)\n- Ignoring discoveries that should change plan (drift)\n- Changes without noting them (invisible drift)\n- Deferring everything (never learning)\n- Large rewrites without user approval\n",{"name":5,"description":7},"main","1ad262fc695612ff484ee364ff66ab5298bdda58","skills\u002Fws.refine",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-refine",{"tool":36,"command":37},"bunx","bunx skills add vempio\u002FWhittleSpec --skill ws-refine",{"tool":39,"command":40},"pnpm","pnpm dlx skills add vempio\u002FWhittleSpec --skill ws-refine","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvempio\u002FWhittleSpec\u002Fblob\u002Fmain\u002Fskills\u002Fws.refine\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},"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":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},"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":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},"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":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},"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",[],[]]