planning-and-task-breakdown
Installation
SKILL.md
Planning & Task Breakdown
Decompose specifications into clear execution steps (workflow/<change-slug>/PLAN.md) and, when warranted, small verifiable tasks (workflow/<change-slug>/TASKS.md) before writing any implementation code.
Language & Architecture Agnostic: This skill applies to any technology stack, domain, or project structure. Reason in terms of deliverables, boundaries, dependencies, and verification—never assume specific languages, frameworks, or architectural patterns.
Core Rule
Plan in read-only mode. Explore the repository, map dependencies, and write the plan before modifying any deliverable files. Do not start implementing while planning.
When to Apply
- Translating
workflow/<change-slug>/SPEC.mdinto an actionable execution plan (workflow/<change-slug>/PLAN.md). - Work feels too large, ambiguous, or multi-faceted to execute in a single pass.
- Multiple independent deliverables or parallel/asynchronous agent executions are possible.
- Skip formal breakdown for trivial, single-step edits where planning adds no value.