[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79B0JBNT5Z9YF6KP5PGPXB3":3,"skill-same:01M79B0JBNT5Z9YF6KP5PGPXB3":46},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M79B0JBNT5Z9YF6KP5PGPXB3","planning-and-task-breakdown",null,"Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.","CCH-HQ\u002Fcchp-automation","CCH-HQ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F253065381?v=4","01M79AG9QPRTJEVTCT1ZS7TM9J","CCH HQ","01M79AG9RNM4TAB3PJQH71X62P",2,"MIT","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fplanning-and-task-breakdown\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: planning-and-task-breakdown\ndescription: Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.\n---\n\n# Planning and Task Breakdown\n\n## Overview\n\nDecompose work into small, verifiable tasks with explicit acceptance criteria. Good task breakdown is the difference between an agent that completes work reliably and one that produces a tangled mess. Every task should be small enough to implement, test, and verify in a single focused session.\n\n## When to Use\n\n- You have a spec and need to break it into implementable units\n- A task feels too large or vague to start\n- Work needs to be parallelized across multiple agents or sessions\n- You need to communicate scope to a human\n- The implementation order isn't obvious\n\n**When NOT to use:** Single-file changes with obvious scope, or when the spec already contains well-defined tasks.\n\n## The Planning Process\n\n### Step 1: Enter Plan Mode\n\nBefore writing any code, operate in read-only mode:\n\n- Read the spec and relevant codebase sections\n- Identify existing patterns and conventions\n- Map dependencies between components\n- Note risks and unknowns\n\n**Do NOT write code during planning.** The output is a plan document saved to `tasks\u002Fplan.md` and a task list saved to `tasks\u002Ftodo.md`, not implementation.\n\n### Step 2: Identify the Dependency Graph\n\nMap what depends on what:\n\n```\nDatabase schema\n    │\n    ├── API models\u002Ftypes\n    │       │\n    │       ├── API endpoints\n    │       │       │\n    │       │       └── Frontend API client\n    │       │               │\n    │       │               └── UI components\n    │       │\n    │       └── Validation logic\n    │\n    └── Seed data \u002F migrations\n```\n\nImplementation order follows the dependency graph bottom-up: build foundations first.\n\n### Step 3: Slice Vertically\n\nInstead of building all the database, then all the API, then all the UI — build one complete feature path at a time:\n\n**Bad (horizontal slicing):**\n```\nTask 1: Build entire database schema\nTask 2: Build all API endpoints\nTask 3: Build all UI components\nTask 4: Connect everything\n```\n\n**Good (vertical slicing):**\n```\nTask 1: User can create an account (schema + API + UI for registration)\nTask 2: User can log in (auth schema + API + UI for login)\nTask 3: User can create a task (task schema + API + UI for creation)\nTask 4: User can view task list (query + API + UI for list view)\n```\n\nEach vertical slice delivers working, testable functionality.\n\n### Step 4: Write Tasks\n\nEach task follows this structure:\n\n```markdown\n## Task [N]: [Short descriptive title]\n\n**Description:** One paragraph explaining what this task accomplishes.\n\n**Acceptance criteria:**\n- [ ] [Specific, testable condition]\n- [ ] [Specific, testable condition]\n\n**Verification:**\n- [ ] Tests pass: [the repository's focused-test command]\n- [ ] Build succeeds: [the repository's build command]\n- [ ] Manual check: [description of what to verify]\n\n**Dependencies:** [Task numbers this depends on, or \"None\"]\n\n**Files likely touched:**\n- `src\u002Fpath\u002Fto\u002Ffile.ts`\n- `tests\u002Fpath\u002Fto\u002Ftest.ts`\n\n**Estimated scope:** [Small: 1-2 files | Medium: 3-5 files | Large: 5+ files]\n```\n\n### Step 5: Order and Checkpoint\n\nArrange tasks so that:\n\n1. Dependencies are satisfied (build foundation first)\n2. Each task leaves the system in a working state\n3. Verification checkpoints occur after every 2-3 tasks\n4. High-risk tasks are early (fail fast)\n\nAdd explicit checkpoints:\n\n```markdown\n## Checkpoint: After Tasks 1-3\n- [ ] All tests pass\n- [ ] Application builds without errors\n- [ ] Core user flow works end-to-end\n- [ ] Review with human before proceeding\n```\n\n## Task Sizing Guidelines\n\n| Size | Files | Scope | Example |\n|------|-------|-------|---------|\n| **XS** | 1 | Single function or config change | Add a validation rule |\n| **S** | 1-2 | One component or endpoint | Add a new API endpoint |\n| **M** | 3-5 | One feature slice | User registration flow |\n| **L** | 5-8 | Multi-component feature | Search with filtering and pagination |\n| **XL** | 8+ | **Too large — break it down further** | — |\n\nIf a task is L or larger, it should be broken into smaller tasks. An agent performs best on S and M tasks.\n\n**When to break a task down further:**\n- It would take more than one focused session (roughly 2+ hours of agent work)\n- You cannot describe the acceptance criteria in 3 or fewer bullet points\n- It touches two or more independent subsystems (e.g., auth and billing)\n- You find yourself writing \"and\" in the task title (a sign it is two tasks)\n\n## Output Files\n\n- **Plan document:** Save the implementation plan to `tasks\u002Fplan.md`.\n- **Task list:** Save the checklist-style task list to `tasks\u002Ftodo.md`.\n\nCreate the `tasks\u002F` directory if it does not exist. These paths are the convention expected by the `\u002Fbuild` command and other downstream tooling.\n\n## Plan Document Template\n\n```markdown\n# Implementation Plan: [Feature\u002FProject Name]\n\n## Overview\n[One paragraph summary of what we're building]\n\n## Architecture Decisions\n- [Key decision 1 and rationale]\n- [Key decision 2 and rationale]\n\n## Task List\n\n### Phase 1: Foundation\n- [ ] Task 1: ...\n- [ ] Task 2: ...\n\n### Checkpoint: Foundation\n- [ ] Tests pass, builds clean\n\n### Phase 2: Core Features\n- [ ] Task 3: ...\n- [ ] Task 4: ...\n\n### Checkpoint: Core Features\n- [ ] End-to-end flow works\n\n### Phase 3: Polish\n- [ ] Task 5: ...\n- [ ] Task 6: ...\n\n### Checkpoint: Complete\n- [ ] All acceptance criteria met\n- [ ] Ready for review\n\n## Risks and Mitigations\n| Risk | Impact | Mitigation |\n|------|--------|------------|\n| [Risk] | [High\u002FMed\u002FLow] | [Strategy] |\n\n## Open Questions\n- [Question needing human input]\n```\n\n## Parallelization Opportunities\n\nWhen multiple agents or sessions are available:\n\n- **Safe to parallelize:** Independent feature slices, tests for already-implemented features, documentation\n- **Must be sequential:** Database migrations, shared state changes, dependency chains\n- **Needs coordination:** Features that share an API contract (define the contract first, then parallelize)\n\n## Common Rationalizations\n\n| Rationalization | Reality |\n|---|---|\n| \"I'll figure it out as I go\" | That's how you end up with a tangled mess and rework. 10 minutes of planning saves hours. |\n| \"The tasks are obvious\" | Write them down anyway. Explicit tasks surface hidden dependencies and forgotten edge cases. |\n| \"Planning is overhead\" | Planning is the task. Implementation without a plan is just typing. |\n| \"I can hold it all in my head\" | Context windows are finite. Written plans survive session boundaries and compaction. |\n\n## Red Flags\n\n- Starting implementation without a written task list\n- Tasks that say \"implement the feature\" without acceptance criteria\n- No verification steps in the plan\n- All tasks are XL-sized\n- No checkpoints between tasks\n- Dependency order isn't considered\n\n## Verification\n\nBefore starting implementation, confirm:\n\n- [ ] Every task has acceptance criteria\n- [ ] Every task has a verification step\n- [ ] Task dependencies are identified and ordered correctly\n- [ ] No task touches more than ~5 files\n- [ ] Checkpoints exist between major phases\n- [ ] The human has reviewed and approved the plan\n\n## See Also\n\nAcceptance criteria are per-task and answer \"did we build the right thing?\". They sit on top of the project-wide Definition of Done, the standing bar every task clears before it counts as done. See `references\u002Fdefinition-of-done.md`.\n","# Planning and Task Breakdown\n\n## Overview\n\nDecompose work into small, verifiable tasks with explicit acceptance criteria. Good task breakdown is the difference between an agent that completes work reliably and one that produces a tangled mess. Every task should be small enough to implement, test, and verify in a single focused session.\n\n## When to Use\n\n- You have a spec and need to break it into implementable units\n- A task feels too large or vague to start\n- Work needs to be parallelized across multiple agents or sessions\n- You need to communicate scope to a human\n- The implementation order isn't obvious\n\n**When NOT to use:** Single-file changes with obvious scope, or when the spec already contains well-defined tasks.\n\n## The Planning Process\n\n### Step 1: Enter Plan Mode\n\nBefore writing any code, operate in read-only mode:\n\n- Read the spec and relevant codebase sections\n- Identify existing patterns and conventions\n- Map dependencies between components\n- Note risks and unknowns\n\n**Do NOT write code during planning.** The output is a plan document saved to `tasks\u002Fplan.md` and a task list saved to `tasks\u002Ftodo.md`, not implementation.\n\n### Step 2: Identify the Dependency Graph\n\nMap what depends on what:\n\n```\nDatabase schema\n    │\n    ├── API models\u002Ftypes\n    │       │\n    │       ├── API endpoints\n    │       │       │\n    │       │       └── Frontend API client\n    │       │               │\n    │       │               └── UI components\n    │       │\n    │       └── Validation logic\n    │\n    └── Seed data \u002F migrations\n```\n\nImplementation order follows the dependency graph bottom-up: build foundations first.\n\n### Step 3: Slice Vertically\n\nInstead of building all the database, then all the API, then all the UI — build one complete feature path at a time:\n\n**Bad (horizontal slicing):**\n```\nTask 1: Build entire database schema\nTask 2: Build all API endpoints\nTask 3: Build all UI components\nTask 4: Connect everything\n```\n\n**Good (vertical slicing):**\n```\nTask 1: User can create an account (schema + API + UI for registration)\nTask 2: User can log in (auth schema + API + UI for login)\nTask 3: User can create a task (task schema + API + UI for creation)\nTask 4: User can view task list (query + API + UI for list view)\n```\n\nEach vertical slice delivers working, testable functionality.\n\n### Step 4: Write Tasks\n\nEach task follows this structure:\n\n```markdown\n## Task [N]: [Short descriptive title]\n\n**Description:** One paragraph explaining what this task accomplishes.\n\n**Acceptance criteria:**\n- [ ] [Specific, testable condition]\n- [ ] [Specific, testable condition]\n\n**Verification:**\n- [ ] Tests pass: [the repository's focused-test command]\n- [ ] Build succeeds: [the repository's build command]\n- [ ] Manual check: [description of what to verify]\n\n**Dependencies:** [Task numbers this depends on, or \"None\"]\n\n**Files likely touched:**\n- `src\u002Fpath\u002Fto\u002Ffile.ts`\n- `tests\u002Fpath\u002Fto\u002Ftest.ts`\n\n**Estimated scope:** [Small: 1-2 files | Medium: 3-5 files | Large: 5+ files]\n```\n\n### Step 5: Order and Checkpoint\n\nArrange tasks so that:\n\n1. Dependencies are satisfied (build foundation first)\n2. Each task leaves the system in a working state\n3. Verification checkpoints occur after every 2-3 tasks\n4. High-risk tasks are early (fail fast)\n\nAdd explicit checkpoints:\n\n```markdown\n## Checkpoint: After Tasks 1-3\n- [ ] All tests pass\n- [ ] Application builds without errors\n- [ ] Core user flow works end-to-end\n- [ ] Review with human before proceeding\n```\n\n## Task Sizing Guidelines\n\n| Size | Files | Scope | Example |\n|------|-------|-------|---------|\n| **XS** | 1 | Single function or config change | Add a validation rule |\n| **S** | 1-2 | One component or endpoint | Add a new API endpoint |\n| **M** | 3-5 | One feature slice | User registration flow |\n| **L** | 5-8 | Multi-component feature | Search with filtering and pagination |\n| **XL** | 8+ | **Too large — break it down further** | — |\n\nIf a task is L or larger, it should be broken into smaller tasks. An agent performs best on S and M tasks.\n\n**When to break a task down further:**\n- It would take more than one focused session (roughly 2+ hours of agent work)\n- You cannot describe the acceptance criteria in 3 or fewer bullet points\n- It touches two or more independent subsystems (e.g., auth and billing)\n- You find yourself writing \"and\" in the task title (a sign it is two tasks)\n\n## Output Files\n\n- **Plan document:** Save the implementation plan to `tasks\u002Fplan.md`.\n- **Task list:** Save the checklist-style task list to `tasks\u002Ftodo.md`.\n\nCreate the `tasks\u002F` directory if it does not exist. These paths are the convention expected by the `\u002Fbuild` command and other downstream tooling.\n\n## Plan Document Template\n\n```markdown\n# Implementation Plan: [Feature\u002FProject Name]\n\n## Overview\n[One paragraph summary of what we're building]\n\n## Architecture Decisions\n- [Key decision 1 and rationale]\n- [Key decision 2 and rationale]\n\n## Task List\n\n### Phase 1: Foundation\n- [ ] Task 1: ...\n- [ ] Task 2: ...\n\n### Checkpoint: Foundation\n- [ ] Tests pass, builds clean\n\n### Phase 2: Core Features\n- [ ] Task 3: ...\n- [ ] Task 4: ...\n\n### Checkpoint: Core Features\n- [ ] End-to-end flow works\n\n### Phase 3: Polish\n- [ ] Task 5: ...\n- [ ] Task 6: ...\n\n### Checkpoint: Complete\n- [ ] All acceptance criteria met\n- [ ] Ready for review\n\n## Risks and Mitigations\n| Risk | Impact | Mitigation |\n|------|--------|------------|\n| [Risk] | [High\u002FMed\u002FLow] | [Strategy] |\n\n## Open Questions\n- [Question needing human input]\n```\n\n## Parallelization Opportunities\n\nWhen multiple agents or sessions are available:\n\n- **Safe to parallelize:** Independent feature slices, tests for already-implemented features, documentation\n- **Must be sequential:** Database migrations, shared state changes, dependency chains\n- **Needs coordination:** Features that share an API contract (define the contract first, then parallelize)\n\n## Common Rationalizations\n\n| Rationalization | Reality |\n|---|---|\n| \"I'll figure it out as I go\" | That's how you end up with a tangled mess and rework. 10 minutes of planning saves hours. |\n| \"The tasks are obvious\" | Write them down anyway. Explicit tasks surface hidden dependencies and forgotten edge cases. |\n| \"Planning is overhead\" | Planning is the task. Implementation without a plan is just typing. |\n| \"I can hold it all in my head\" | Context windows are finite. Written plans survive session boundaries and compaction. |\n\n## Red Flags\n\n- Starting implementation without a written task list\n- Tasks that say \"implement the feature\" without acceptance criteria\n- No verification steps in the plan\n- All tasks are XL-sized\n- No checkpoints between tasks\n- Dependency order isn't considered\n\n## Verification\n\nBefore starting implementation, confirm:\n\n- [ ] Every task has acceptance criteria\n- [ ] Every task has a verification step\n- [ ] Task dependencies are identified and ordered correctly\n- [ ] No task touches more than ~5 files\n- [ ] Checkpoints exist between major phases\n- [ ] The human has reviewed and approved the plan\n\n## See Also\n\nAcceptance criteria are per-task and answer \"did we build the right thing?\". They sit on top of the project-wide Definition of Done, the standing bar every task clears before it counts as done. See `references\u002Fdefinition-of-done.md`.\n",{"name":5,"description":7},"main","a93764baed707eda5a68d91e19e5719368e6335e","skills-backup\u002Fskills\u002Fplanning-and-task-breakdown",0,"https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation","https:\u002F\u002Fgithub.com\u002FCCH-HQ","https:\u002F\u002Fclaude-code-hub.app\u002F","2026-11-09 20:50:54",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add CCH-HQ\u002Fcchp-automation --skill planning-and-task-breakdown",{"tool":38,"command":39},"bunx","bunx skills add CCH-HQ\u002Fcchp-automation --skill planning-and-task-breakdown",{"tool":41,"command":42},"pnpm","pnpm dlx skills add CCH-HQ\u002Fcchp-automation --skill planning-and-task-breakdown","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fplanning-and-task-breakdown\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M79B44RKSB6Z0GENGYFCCZYA","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79B410BHDSNHZ7MKAYXWJHS","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79B3XK29MCD5HGD50YGYXQZ","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79B3TFQEXXM2KK5V44H64DV","wayfinder","Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79B3Q3WTMJDM6NNGG1X4NYK","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\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79B3GW8YCKT7W489HKWFMNC","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[],[]]