[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M731AS9N89S2E50MSW2Y9QYY":3,"skill-same:01M731AS9N89S2E50MSW2Y9QYY":64},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":47,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M731AS9N89S2E50MSW2Y9QYY","writing-plans",null,"Write implementation plans: bite-sized tasks, paths, code.","StarryCod\u002Fcogitum","StarryCod","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F200964623?v=4","01M7311AM3RY259SYKGHWBEDN0","OpenReason","01M7311AMRC1PBSTYZWSD1AQFJ",12,"MIT","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Fwriting-plans\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: writing-plans\ndescription: \"Write implementation plans: bite-sized tasks, paths, code.\"\nversion: 1.1.0\nauthor: Cogitum (adapted from obra\u002Fsuperpowers)\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  cogitum:\n    tags: [planning, design, implementation, workflow, documentation]\n    related_skills: [subagent-driven-development, test-driven-development, requesting-code-review]\n---\n\n# Writing Implementation Plans\n\n## Overview\n\nWrite comprehensive implementation plans assuming the implementer has zero context for the codebase and questionable taste. Document everything they need: which files to touch, complete code, testing commands, docs to check, how to verify. Give them bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.\n\nAssume the implementer is a skilled developer but knows almost nothing about the toolset or problem domain. Assume they don't know good test design very well.\n\n**Core principle:** A good plan makes implementation obvious. If someone has to guess, the plan is incomplete.\n\n## When to Use\n\n**Always use before:**\n- Implementing multi-step features\n- Breaking down complex requirements\n- Delegating to subagents via subagent-driven-development\n\n**Don't skip when:**\n- Feature seems simple (assumptions cause bugs)\n- You plan to implement it yourself (future you needs guidance)\n- Working alone (documentation matters)\n\n## Bite-Sized Task Granularity\n\n**Each task = 2-5 minutes of focused work.**\n\nEvery step is one action:\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\n\n**Too big:**\n```markdown\n### Task 1: Build authentication system\n[50 lines of code across 5 files]\n```\n\n**Right size:**\n```markdown\n### Task 1: Create User model with email field\n[10 lines, 1 file]\n\n### Task 2: Add password hash field to User\n[8 lines, 1 file]\n\n### Task 3: Create password hashing utility\n[15 lines, 1 file]\n```\n\n## Plan Document Structure\n\n### Header (Required)\n\nEvery plan MUST start with:\n\n```markdown\n# [Feature Name] Implementation Plan\n\n> **For Cogitum:** Use subagent-driven-development skill to implement this plan task-by-task.\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\nEach task follows this format:\n\n````markdown\n### Task N: [Descriptive Name]\n\n**Objective:** What this task accomplishes (one sentence)\n\n**Files:**\n- Create: `exact\u002Fpath\u002Fto\u002Fnew_file.py`\n- Modify: `exact\u002Fpath\u002Fto\u002Fexisting.py:45-67` (line numbers if known)\n- Test: `tests\u002Fpath\u002Fto\u002Ftest_file.py`\n\n**Step 1: Write 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 failure**\n\nRun: `pytest tests\u002Fpath\u002Ftest.py::test_specific_behavior -v`\nExpected: FAIL — \"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 pass**\n\nRun: `pytest tests\u002Fpath\u002Ftest.py::test_specific_behavior -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: add specific feature\"\n```\n````\n\n## Writing Process\n\n### Step 1: Understand Requirements\n\nRead and understand:\n- Feature requirements\n- Design documents or user description\n- Acceptance criteria\n- Constraints\n\n### Step 2: Explore the Codebase\n\nUse Cogitum tools to understand the project:\n\n```python\n# Understand project structure\nsearch_files(\"*.py\", target=\"files\", path=\"src\u002F\")\n\n# Look at similar features\nsearch_files(\"similar_pattern\", path=\"src\u002F\", file_glob=\"*.py\")\n\n# Check existing tests\nsearch_files(\"*.py\", target=\"files\", path=\"tests\u002F\")\n\n# Read key files\nread_file(\"src\u002Fapp.py\")\n```\n\n### Step 3: Design Approach\n\nDecide:\n- Architecture pattern\n- File organization\n- Dependencies needed\n- Testing strategy\n\n### Step 4: Write Tasks\n\nCreate tasks in order:\n1. Setup\u002Finfrastructure\n2. Core functionality (TDD for each)\n3. Edge cases\n4. Integration\n5. Cleanup\u002Fdocumentation\n\n### Step 5: Add Complete Details\n\nFor each task, include:\n- **Exact file paths** (not \"the config file\" but `src\u002Fconfig\u002Fsettings.py`)\n- **Complete code examples** (not \"add validation\" but the actual code)\n- **Exact commands** with expected output\n- **Verification steps** that prove the task works\n\n### Step 6: Review the Plan\n\nCheck:\n- [ ] Tasks are sequential and logical\n- [ ] Each task is bite-sized (2-5 min)\n- [ ] File paths are exact\n- [ ] Code examples are complete (copy-pasteable)\n- [ ] Commands are exact with expected output\n- [ ] No missing context\n- [ ] DRY, YAGNI, TDD principles applied\n\n### Step 7: Save the Plan\n\n```bash\nmkdir -p docs\u002Fplans\n# Save plan to docs\u002Fplans\u002FYYYY-MM-DD-feature-name.md\ngit add docs\u002Fplans\u002F\ngit commit -m \"docs: add implementation plan for [feature]\"\n```\n\n## Principles\n\n### DRY (Don't Repeat Yourself)\n\n**Bad:** Copy-paste validation in 3 places\n**Good:** Extract validation function, use everywhere\n\n### YAGNI (You Aren't Gonna Need It)\n\n**Bad:** Add \"flexibility\" for future requirements\n**Good:** Implement only what's needed now\n\n```python\n# Bad — YAGNI violation\nclass User:\n    def __init__(self, name, email):\n        self.name = name\n        self.email = email\n        self.preferences = {}  # Not needed yet!\n        self.metadata = {}     # Not needed yet!\n\n# Good — YAGNI\nclass User:\n    def __init__(self, name, email):\n        self.name = name\n        self.email = email\n```\n\n### TDD (Test-Driven Development)\n\nEvery task that produces code should include the full TDD cycle:\n1. Write failing test\n2. Run to verify failure\n3. Write minimal code\n4. Run to verify pass\n\nSee `test-driven-development` skill for details.\n\n### Frequent Commits\n\nCommit after every task:\n```bash\ngit add [files]\ngit commit -m \"type: description\"\n```\n\n## Common Mistakes\n\n### Vague Tasks\n\n**Bad:** \"Add authentication\"\n**Good:** \"Create User model with email and password_hash fields\"\n\n### Incomplete Code\n\n**Bad:** \"Step 1: Add validation function\"\n**Good:** \"Step 1: Add validation function\" followed by the complete function code\n\n### Missing Verification\n\n**Bad:** \"Step 3: Test it works\"\n**Good:** \"Step 3: Run `pytest tests\u002Ftest_auth.py -v`, expected: 3 passed\"\n\n### Missing File Paths\n\n**Bad:** \"Create the model file\"\n**Good:** \"Create: `src\u002Fmodels\u002Fuser.py`\"\n\n## Execution Handoff\n\nAfter saving the plan, offer the execution approach:\n\n**\"Plan complete and saved. Ready to execute using subagent-driven-development — I'll dispatch a fresh subagent per task with two-stage review (spec compliance then code quality). Shall I proceed?\"**\n\nWhen executing, use the `subagent-driven-development` skill:\n- Fresh `delegate_task` per task with full context\n- Spec compliance review after each task\n- Code quality review after spec passes\n- Proceed only when both reviews approve\n\n## Remember\n\n```\nBite-sized tasks (2-5 min each)\nExact file paths\nComplete code (copy-pasteable)\nExact commands with expected output\nVerification steps\nDRY, YAGNI, TDD\nFrequent commits\n```\n\n**A good plan makes implementation obvious.**\n","# Writing Implementation Plans\n\n## Overview\n\nWrite comprehensive implementation plans assuming the implementer has zero context for the codebase and questionable taste. Document everything they need: which files to touch, complete code, testing commands, docs to check, how to verify. Give them bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.\n\nAssume the implementer is a skilled developer but knows almost nothing about the toolset or problem domain. Assume they don't know good test design very well.\n\n**Core principle:** A good plan makes implementation obvious. If someone has to guess, the plan is incomplete.\n\n## When to Use\n\n**Always use before:**\n- Implementing multi-step features\n- Breaking down complex requirements\n- Delegating to subagents via subagent-driven-development\n\n**Don't skip when:**\n- Feature seems simple (assumptions cause bugs)\n- You plan to implement it yourself (future you needs guidance)\n- Working alone (documentation matters)\n\n## Bite-Sized Task Granularity\n\n**Each task = 2-5 minutes of focused work.**\n\nEvery step is one action:\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\n\n**Too big:**\n```markdown\n### Task 1: Build authentication system\n[50 lines of code across 5 files]\n```\n\n**Right size:**\n```markdown\n### Task 1: Create User model with email field\n[10 lines, 1 file]\n\n### Task 2: Add password hash field to User\n[8 lines, 1 file]\n\n### Task 3: Create password hashing utility\n[15 lines, 1 file]\n```\n\n## Plan Document Structure\n\n### Header (Required)\n\nEvery plan MUST start with:\n\n```markdown\n# [Feature Name] Implementation Plan\n\n> **For Cogitum:** Use subagent-driven-development skill to implement this plan task-by-task.\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\nEach task follows this format:\n\n````markdown\n### Task N: [Descriptive Name]\n\n**Objective:** What this task accomplishes (one sentence)\n\n**Files:**\n- Create: `exact\u002Fpath\u002Fto\u002Fnew_file.py`\n- Modify: `exact\u002Fpath\u002Fto\u002Fexisting.py:45-67` (line numbers if known)\n- Test: `tests\u002Fpath\u002Fto\u002Ftest_file.py`\n\n**Step 1: Write 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 failure**\n\nRun: `pytest tests\u002Fpath\u002Ftest.py::test_specific_behavior -v`\nExpected: FAIL — \"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 pass**\n\nRun: `pytest tests\u002Fpath\u002Ftest.py::test_specific_behavior -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: add specific feature\"\n```\n````\n\n## Writing Process\n\n### Step 1: Understand Requirements\n\nRead and understand:\n- Feature requirements\n- Design documents or user description\n- Acceptance criteria\n- Constraints\n\n### Step 2: Explore the Codebase\n\nUse Cogitum tools to understand the project:\n\n```python\n# Understand project structure\nsearch_files(\"*.py\", target=\"files\", path=\"src\u002F\")\n\n# Look at similar features\nsearch_files(\"similar_pattern\", path=\"src\u002F\", file_glob=\"*.py\")\n\n# Check existing tests\nsearch_files(\"*.py\", target=\"files\", path=\"tests\u002F\")\n\n# Read key files\nread_file(\"src\u002Fapp.py\")\n```\n\n### Step 3: Design Approach\n\nDecide:\n- Architecture pattern\n- File organization\n- Dependencies needed\n- Testing strategy\n\n### Step 4: Write Tasks\n\nCreate tasks in order:\n1. Setup\u002Finfrastructure\n2. Core functionality (TDD for each)\n3. Edge cases\n4. Integration\n5. Cleanup\u002Fdocumentation\n\n### Step 5: Add Complete Details\n\nFor each task, include:\n- **Exact file paths** (not \"the config file\" but `src\u002Fconfig\u002Fsettings.py`)\n- **Complete code examples** (not \"add validation\" but the actual code)\n- **Exact commands** with expected output\n- **Verification steps** that prove the task works\n\n### Step 6: Review the Plan\n\nCheck:\n- [ ] Tasks are sequential and logical\n- [ ] Each task is bite-sized (2-5 min)\n- [ ] File paths are exact\n- [ ] Code examples are complete (copy-pasteable)\n- [ ] Commands are exact with expected output\n- [ ] No missing context\n- [ ] DRY, YAGNI, TDD principles applied\n\n### Step 7: Save the Plan\n\n```bash\nmkdir -p docs\u002Fplans\n# Save plan to docs\u002Fplans\u002FYYYY-MM-DD-feature-name.md\ngit add docs\u002Fplans\u002F\ngit commit -m \"docs: add implementation plan for [feature]\"\n```\n\n## Principles\n\n### DRY (Don't Repeat Yourself)\n\n**Bad:** Copy-paste validation in 3 places\n**Good:** Extract validation function, use everywhere\n\n### YAGNI (You Aren't Gonna Need It)\n\n**Bad:** Add \"flexibility\" for future requirements\n**Good:** Implement only what's needed now\n\n```python\n# Bad — YAGNI violation\nclass User:\n    def __init__(self, name, email):\n        self.name = name\n        self.email = email\n        self.preferences = {}  # Not needed yet!\n        self.metadata = {}     # Not needed yet!\n\n# Good — YAGNI\nclass User:\n    def __init__(self, name, email):\n        self.name = name\n        self.email = email\n```\n\n### TDD (Test-Driven Development)\n\nEvery task that produces code should include the full TDD cycle:\n1. Write failing test\n2. Run to verify failure\n3. Write minimal code\n4. Run to verify pass\n\nSee `test-driven-development` skill for details.\n\n### Frequent Commits\n\nCommit after every task:\n```bash\ngit add [files]\ngit commit -m \"type: description\"\n```\n\n## Common Mistakes\n\n### Vague Tasks\n\n**Bad:** \"Add authentication\"\n**Good:** \"Create User model with email and password_hash fields\"\n\n### Incomplete Code\n\n**Bad:** \"Step 1: Add validation function\"\n**Good:** \"Step 1: Add validation function\" followed by the complete function code\n\n### Missing Verification\n\n**Bad:** \"Step 3: Test it works\"\n**Good:** \"Step 3: Run `pytest tests\u002Ftest_auth.py -v`, expected: 3 passed\"\n\n### Missing File Paths\n\n**Bad:** \"Create the model file\"\n**Good:** \"Create: `src\u002Fmodels\u002Fuser.py`\"\n\n## Execution Handoff\n\nAfter saving the plan, offer the execution approach:\n\n**\"Plan complete and saved. Ready to execute using subagent-driven-development — I'll dispatch a fresh subagent per task with two-stage review (spec compliance then code quality). Shall I proceed?\"**\n\nWhen executing, use the `subagent-driven-development` skill:\n- Fresh `delegate_task` per task with full context\n- Spec compliance review after each task\n- Code quality review after spec passes\n- Proceed only when both reviews approve\n\n## Remember\n\n```\nBite-sized tasks (2-5 min each)\nExact file paths\nComplete code (copy-pasteable)\nExact commands with expected output\nVerification steps\nDRY, YAGNI, TDD\nFrequent commits\n```\n\n**A good plan makes implementation obvious.**\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":38,"description":7},"Cogitum (adapted from obra\u002Fsuperpowers)","1.1.0",{"cogitum":27},{"tags":28,"related_skills":34},[29,30,31,32,33],"planning","design","implementation","workflow","documentation",[35,36,37],"subagent-driven-development","test-driven-development","requesting-code-review",[39,40,41],"linux","macos","windows","master","a99de210a5d82a24b7aa5020afa1f904f595d14c","cogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Fwriting-plans",0,"https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fcogitum","https:\u002F\u002Fgithub.com\u002FStarryCod","2026-05-25 23:49:07",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add StarryCod\u002Fcogitum --skill writing-plans",{"tool":56,"command":57},"bunx","bunx skills add StarryCod\u002Fcogitum --skill writing-plans",{"tool":59,"command":60},"pnpm","pnpm dlx skills add StarryCod\u002Fcogitum --skill writing-plans","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Fwriting-plans\u002FSKILL.md",true,[],[65,72,79,85,92,98],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M731AYJQFFAGEQ8T8NMPKM72","yuanbao","Yuanbao (元宝) groups: @mention users, query info\u002Fmembers.","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fyuanbao\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M731AWAHBZQ4JG5HBRXSTEWP","tg-moderator","Telegram chat moderator\u002Fcompanion mode. No tools, conversational only.","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Ftg-moderator\u002FSKILL.md",[],[],{"skillNo":80,"name":36,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M731ANESTYGBFV3XSAT0AS8Q","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M731AG1KE7ZHM0P1R890ZVB0","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[],[],{"skillNo":93,"name":35,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M731ABWQ3DTCBY8E6WTYSBTT","Execute plans via delegate_task subagents (2-stage review).","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Fsubagent-driven-development\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M731A85MK4VP1ZZPS7X899CS","spike","Throwaway experiments to validate an idea before build.","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Fspike\u002FSKILL.md",[],[]]