[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ERV2JX5DJV2EHSC6FXHEHN":3,"skill-same:01M6ERV2JX5DJV2EHSC6FXHEHN":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6ERV2JX5DJV2EHSC6FXHEHN","writing-plans",null,"Use when you have a spec or requirements for a multi-step task, before touching code","nocksock\u002Fsuperpowers","nocksock","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F22164?v=4","01M6ERQWRTZARGFM7AX8HB89GZ","Nils Riedemann","01M6ERQWXFH5876Z6HEDH9TWYS",1,"MIT","https:\u002F\u002Fgithub.com\u002Fnocksock\u002Fsuperpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37],"writing","writing plans","plans","spec","code","use","task","requirements","multi","2026-11-10 10:12:30",false,"---\nname: writing-plans\ndescription: Use when you have a spec or requirements for a multi-step task, before touching code\n---\n\n# Writing Plans\n\n## Overview\n\nWrite comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD.\n\nAssume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.\n\n**Announce at start:** \"I'm using the writing-plans skill to create the implementation plan.\"\n\n## Commit Preference (Check or Ask)\n\n**First, check if a commit preference was already set this session** (e.g., by deep-work-session).\n\n**If already set:** Use that preference. Don't ask again.\n\n**If not set, use the question tool to ask:**\n> \"Should commits be included as steps in this plan?\"\n> Options: Yes, No\n\n**If No:**\n- Remove all commit steps from the plan\n- Replace \"frequent commits\" guidance with \"frequent saves\u002Fcheckpoints\"\n- This preference applies for the **entire session**, including any future skill invocations\n- The agent MUST NOT commit unless the user **explicitly gives permission** later\n\n**If Yes (or user doesn't specify):**\n- Include commit steps as normal\n- Follow standard \"frequent commits\" guidance\n\n**Context:** This should be run in a dedicated worktree (created by brainstorming skill).\n\n**Save plans to:** `docs\u002Fsuperpowers\u002Fplans\u002FYYYY-MM-DD-\u003Cfeature-name>.md`\n- (User preferences for plan location override this default)\n\n## Scope Check\n\nIf the spec covers multiple independent subsystems, it should have been broken into sub-project specs during brainstorming. If it wasn't, suggest breaking this into separate plans — one per subsystem. Each plan should produce working, testable software on its own.\n\n## File Structure\n\nBefore defining tasks, map out which files will be created or modified and what each one is responsible for. This is where decomposition decisions get locked in.\n\n- Design units with clear boundaries and well-defined interfaces. Each file should have one clear responsibility.\n- You reason best about code you can hold in context at once, and your edits are more reliable when files are focused. Prefer smaller, focused files over large ones that do too much.\n- Files that change together should live together. Split by responsibility, not by technical layer.\n- In existing codebases, follow established patterns. If the codebase uses large files, don't unilaterally restructure - but if a file you're modifying has grown unwieldy, including a split in the plan is reasonable.\n\nThis structure informs the task decomposition. Each task should produce self-contained changes that make sense independently.\n\n## Bite-Sized Task Granularity\n\n**Each step is one action (2-5 minutes):**\n- \"Write the failing test\" - step\n- \"Run it to make sure it fails\" - step\n- \"Implement the minimal code to make the test pass\" - step\n- \"Run the tests and make sure they pass\" - step\n- \"Commit\" - step (only if user opted in to commits)\n\n## Plan Document Header\n\n**Every plan MUST start with this header:**\n\n```markdown\n# [Feature Name] Implementation Plan\n\n> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.\n\n**Goal:** [One sentence describing what this builds]\n\n**Architecture:** [2-3 sentences about approach]\n\n**Tech Stack:** [Key technologies\u002Flibraries]\n\n---\n```\n\n## Task Structure\n\n````markdown\n### Task N: [Component Name]\n\n**Files:**\n- Create: `exact\u002Fpath\u002Fto\u002Ffile.py`\n- Modify: `exact\u002Fpath\u002Fto\u002Fexisting.py:123-145`\n- Test: `tests\u002Fexact\u002Fpath\u002Fto\u002Ftest.py`\n\n- [ ] **Step 1: Write the failing test**\n\n```python\ndef test_specific_behavior():\n    result = function(input)\n    assert result == expected\n```\n\n- [ ] **Step 2: Run test to verify it fails**\n\nRun: `pytest tests\u002Fpath\u002Ftest.py::test_name -v`\nExpected: FAIL with \"function not defined\"\n\n- [ ] **Step 3: Write minimal implementation**\n\n```python\ndef function(input):\n    return expected\n```\n\n- [ ] **Step 4: Run test to verify it passes**\n\nRun: `pytest tests\u002Fpath\u002Ftest.py::test_name -v`\nExpected: PASS\n\n- [ ] **Step 5: Commit**\n\n```bash\ngit add tests\u002Fpath\u002Ftest.py src\u002Fpath\u002Ffile.py\ngit commit -m \"feat(scope): add specific feature\"\n```\n````\n\n## Remember\n- Exact file paths always\n- Complete code in plan (not \"add validation\")\n- Exact commands with expected output\n- Reference relevant skills with @ syntax\n- DRY, YAGNI, TDD\n- Respect user's commit preference (session-wide)\n- Use superpowers:making-commits for commit steps (conventional format, sizing)\n\n## Plan Review Loop\n\nAfter writing the complete plan:\n\n1. Dispatch a single plan-document-reviewer subagent (see plan-document-reviewer-prompt.md) with precisely crafted review context — never your session history. This keeps the reviewer focused on the plan, not your thought process.\n   - Provide: path to the plan document, path to spec document\n2. If ❌ Issues Found: fix the issues, re-dispatch reviewer for the whole plan\n3. If ✅ Approved: proceed to execution handoff\n\n**Review loop guidance:**\n- Same agent that wrote the plan fixes it (preserves context)\n- If loop exceeds 3 iterations, surface to human for guidance\n- Reviewers are advisory — explain disagreements if you believe feedback is incorrect\n\n## Execution Handoff\n\nAfter saving the plan, check the session's question style before deciding how to proceed.\n\n**\"Plan complete and saved to `docs\u002Fsuperpowers\u002Fplans\u002F\u003Cfilename>.md`. Two execution options:**\n\n**1. Subagent-Driven (recommended)** - I dispatch a fresh subagent per task, review between tasks, fast iteration\n\n**2. Inline Execution** - Execute tasks in this session using executing-plans, batch execution with checkpoints\n\n**Options:**\n1. **Continue in this session** - Start implementation now with subagent-driven execution\n2. **Fresh session for implementation** - Hand off to maximize context for implementation\n\n**If \"Continue in this session\" chosen:**\n- **REQUIRED SUB-SKILL:** Use superpowers:subagent-driven-development\n- Stay in this session, execute autonomously\n\n**If \"Fresh session for implementation\" chosen:**\n- **REQUIRED SUB-SKILL:** Use superpowers:session-handoff\n- Write comprehensive handoff document including all deep work preferences and the plan\n- Note in handoff: \"Planning complete. Ready for implementation phase.\"\n- Provide continuation prompt for fresh session\n\n### Otherwise (Interactive Mode or No Session Context)\n\nUse the question tool to offer execution choice:\n\n**Question:** \"Plan complete and saved. How would you like to execute it?\"\n\n**Options:**\n1. **Subagent-Driven (this session)** - I dispatch fresh subagent per task, review between tasks, fast iteration\n2. **Parallel Session (separate)** - Open new session with executing-plans, batch execution with checkpoints\n\n**If Subagent-Driven chosen:**\n- **REQUIRED SUB-SKILL:** Use superpowers:subagent-driven-development\n- Fresh subagent per task + two-stage review\n\n**If Inline Execution chosen:**\n- **REQUIRED SUB-SKILL:** Use superpowers:executing-plans\n- Batch execution with checkpoints for review\n","# Writing Plans\n\n## Overview\n\nWrite comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD.\n\nAssume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.\n\n**Announce at start:** \"I'm using the writing-plans skill to create the implementation plan.\"\n\n## Commit Preference (Check or Ask)\n\n**First, check if a commit preference was already set this session** (e.g., by deep-work-session).\n\n**If already set:** Use that preference. Don't ask again.\n\n**If not set, use the question tool to ask:**\n> \"Should commits be included as steps in this plan?\"\n> Options: Yes, No\n\n**If No:**\n- Remove all commit steps from the plan\n- Replace \"frequent commits\" guidance with \"frequent saves\u002Fcheckpoints\"\n- This preference applies for the **entire session**, including any future skill invocations\n- The agent MUST NOT commit unless the user **explicitly gives permission** later\n\n**If Yes (or user doesn't specify):**\n- Include commit steps as normal\n- Follow standard \"frequent commits\" guidance\n\n**Context:** This should be run in a dedicated worktree (created by brainstorming skill).\n\n**Save plans to:** `docs\u002Fsuperpowers\u002Fplans\u002FYYYY-MM-DD-\u003Cfeature-name>.md`\n- (User preferences for plan location override this default)\n\n## Scope Check\n\nIf the spec covers multiple independent subsystems, it should have been broken into sub-project specs during brainstorming. If it wasn't, suggest breaking this into separate plans — one per subsystem. Each plan should produce working, testable software on its own.\n\n## File Structure\n\nBefore defining tasks, map out which files will be created or modified and what each one is responsible for. This is where decomposition decisions get locked in.\n\n- Design units with clear boundaries and well-defined interfaces. Each file should have one clear responsibility.\n- You reason best about code you can hold in context at once, and your edits are more reliable when files are focused. Prefer smaller, focused files over large ones that do too much.\n- Files that change together should live together. Split by responsibility, not by technical layer.\n- In existing codebases, follow established patterns. If the codebase uses large files, don't unilaterally restructure - but if a file you're modifying has grown unwieldy, including a split in the plan is reasonable.\n\nThis structure informs the task decomposition. Each task should produce self-contained changes that make sense independently.\n\n## Bite-Sized Task Granularity\n\n**Each step is one action (2-5 minutes):**\n- \"Write the failing test\" - step\n- \"Run it to make sure it fails\" - step\n- \"Implement the minimal code to make the test pass\" - step\n- \"Run the tests and make sure they pass\" - step\n- \"Commit\" - step (only if user opted in to commits)\n\n## Plan Document Header\n\n**Every plan MUST start with this header:**\n\n```markdown\n# [Feature Name] Implementation Plan\n\n> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.\n\n**Goal:** [One sentence describing what this builds]\n\n**Architecture:** [2-3 sentences about approach]\n\n**Tech Stack:** [Key technologies\u002Flibraries]\n\n---\n```\n\n## Task Structure\n\n````markdown\n### Task N: [Component Name]\n\n**Files:**\n- Create: `exact\u002Fpath\u002Fto\u002Ffile.py`\n- Modify: `exact\u002Fpath\u002Fto\u002Fexisting.py:123-145`\n- Test: `tests\u002Fexact\u002Fpath\u002Fto\u002Ftest.py`\n\n- [ ] **Step 1: Write the failing test**\n\n```python\ndef test_specific_behavior():\n    result = function(input)\n    assert result == expected\n```\n\n- [ ] **Step 2: Run test to verify it fails**\n\nRun: `pytest tests\u002Fpath\u002Ftest.py::test_name -v`\nExpected: FAIL with \"function not defined\"\n\n- [ ] **Step 3: Write minimal implementation**\n\n```python\ndef function(input):\n    return expected\n```\n\n- [ ] **Step 4: Run test to verify it passes**\n\nRun: `pytest tests\u002Fpath\u002Ftest.py::test_name -v`\nExpected: PASS\n\n- [ ] **Step 5: Commit**\n\n```bash\ngit add tests\u002Fpath\u002Ftest.py src\u002Fpath\u002Ffile.py\ngit commit -m \"feat(scope): add specific feature\"\n```\n````\n\n## Remember\n- Exact file paths always\n- Complete code in plan (not \"add validation\")\n- Exact commands with expected output\n- Reference relevant skills with @ syntax\n- DRY, YAGNI, TDD\n- Respect user's commit preference (session-wide)\n- Use superpowers:making-commits for commit steps (conventional format, sizing)\n\n## Plan Review Loop\n\nAfter writing the complete plan:\n\n1. Dispatch a single plan-document-reviewer subagent (see plan-document-reviewer-prompt.md) with precisely crafted review context — never your session history. This keeps the reviewer focused on the plan, not your thought process.\n   - Provide: path to the plan document, path to spec document\n2. If ❌ Issues Found: fix the issues, re-dispatch reviewer for the whole plan\n3. If ✅ Approved: proceed to execution handoff\n\n**Review loop guidance:**\n- Same agent that wrote the plan fixes it (preserves context)\n- If loop exceeds 3 iterations, surface to human for guidance\n- Reviewers are advisory — explain disagreements if you believe feedback is incorrect\n\n## Execution Handoff\n\nAfter saving the plan, check the session's question style before deciding how to proceed.\n\n**\"Plan complete and saved to `docs\u002Fsuperpowers\u002Fplans\u002F\u003Cfilename>.md`. Two execution options:**\n\n**1. Subagent-Driven (recommended)** - I dispatch a fresh subagent per task, review between tasks, fast iteration\n\n**2. Inline Execution** - Execute tasks in this session using executing-plans, batch execution with checkpoints\n\n**Options:**\n1. **Continue in this session** - Start implementation now with subagent-driven execution\n2. **Fresh session for implementation** - Hand off to maximize context for implementation\n\n**If \"Continue in this session\" chosen:**\n- **REQUIRED SUB-SKILL:** Use superpowers:subagent-driven-development\n- Stay in this session, execute autonomously\n\n**If \"Fresh session for implementation\" chosen:**\n- **REQUIRED SUB-SKILL:** Use superpowers:session-handoff\n- Write comprehensive handoff document including all deep work preferences and the plan\n- Note in handoff: \"Planning complete. Ready for implementation phase.\"\n- Provide continuation prompt for fresh session\n\n### Otherwise (Interactive Mode or No Session Context)\n\nUse the question tool to offer execution choice:\n\n**Question:** \"Plan complete and saved. How would you like to execute it?\"\n\n**Options:**\n1. **Subagent-Driven (this session)** - I dispatch fresh subagent per task, review between tasks, fast iteration\n2. **Parallel Session (separate)** - Open new session with executing-plans, batch execution with checkpoints\n\n**If Subagent-Driven chosen:**\n- **REQUIRED SUB-SKILL:** Use superpowers:subagent-driven-development\n- Fresh subagent per task + two-stage review\n\n**If Inline Execution chosen:**\n- **REQUIRED SUB-SKILL:** Use superpowers:executing-plans\n- Batch execution with checkpoints for review\n",{"name":5,"description":7},"main","52d2d5a29297631b5e3ff61fbc8ca3c6505a26e2","skills\u002Fwriting-plans",0,"https:\u002F\u002Fgithub.com\u002Fnocksock\u002Fsuperpowers","https:\u002F\u002Fgithub.com\u002Fnocksock","http:\u002F\u002Fbleepbloop.studio\u002F","Hi, I'm Nils. I build interfaces for the web.","2026-03-19 04:55:50",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add nocksock\u002Fsuperpowers --skill writing-plans",{"tool":58,"command":59},"bunx","bunx skills add nocksock\u002Fsuperpowers --skill writing-plans",{"tool":61,"command":62},"pnpm","pnpm dlx skills add nocksock\u002Fsuperpowers --skill writing-plans","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnocksock\u002Fsuperpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-plans\u002FSKILL.md",true,[66],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"plan-document-reviewer-prompt.md","REFERENCE","参考文档",1714,"https:\u002F\u002Fgithub.com\u002Fnocksock\u002Fsuperpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-plans\u002Fplan-document-reviewer-prompt.md",[73,89,106,119,130,145],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":84,"publishedAt":38},"01M6ERV5R58PKM81EH15XEYPMF","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fnocksock\u002Fsuperpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[79,82,83],{"categoryNo":80,"categoryName":81,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[85,29,34,86,87,88],"writing skills","editing","work","deployment",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":100,"publishedAt":38},"01M6ERTZS70NCVS375DTD8HGKE","writing good code","use this skill whenever you write code. it provides a process for creating good, composable apis.","https:\u002F\u002Fgithub.com\u002Fnocksock\u002Fsuperpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-good-code\u002FSKILL.md",[95,96,99],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":97,"categoryName":98,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[29,33,101,91,102,103,104,34,105],"good","composable","write","process","it",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":38},"01M6ERTVVRPKZVWK6M8EXPB5QE","write-review-elixir","Review Elixir code. ALWAYS use this skill before or after you added code written in elixir to ensure high code quality. Also use use this when asked to review existing elixir code.","https:\u002F\u002Fgithub.com\u002Fnocksock\u002Fsuperpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-or-review-elixir\u002FSKILL.md",[],[113,103,114,115,34,116,117,118,33],"elixir","review","write review elixir","elixir code","quality","code quality",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":38},"01M6ERTRAM8PSJ9JTAW5J4ABFD","whats-next","Answers what to do next, what to work on next, where we're at","https:\u002F\u002Fgithub.com\u002Fnocksock\u002Fsuperpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwhats-next\u002FSKILL.md",[],[126,127,128,87,129],"whats next","next","work on","do",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":38},"01M6ERTNG9NT8SQH5FHN91JRTS","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fnocksock\u002Fsuperpowers\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[137,138,139,87,34,140,141,142,143,144],"verification before completion","verification","claim","evidence","commands","complete","output","about",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":38},"01M6ERTJAXFN4Y2ZSKX8CV1DJX","using-superpowers","Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Fnocksock\u002Fsuperpowers\u002Fblob\u002Fmain\u002Fskills\u002Fusing-superpowers\u002FSKILL.md",[],[152,153,154,155,156,34,157,158],"using superpowers","superpowers","how","tool","find","conversation","how to"]