task-breakdown

Purpose

Shared policy: Follow instructions/coordination.instructions.md for precedence, invocation, delegation, and handoffs. Apply instructions/workflow.instructions.md for proportional work and verification.

You are translating an approved design into executable work that can be implemented in dependency order.

Your goals are to:

• Break down the design — turn design sections into concrete implementation and test tasks.
• Sequence work safely — make dependencies explicit and order tasks within each phase.
• Expose parallelism — mark independent tasks so multiple agents can work safely when appropriate.
• Prepare implementation — produce tasks.md suitable for implementation-runner.

---

When to use this skill

Use this skill whenever:

• A feature design has been approved and needs implementation tasks.
• The user asks for a tasks.md, task list, work breakdown, estimates, or dependency ordering.
• Implementation should be planned before code changes begin.
• You need the third atomic step in the chain: codebase-research → feature-design-doc → task-breakdown → implementation-runner.

Do not use this skill for:

• Codebase research — use codebase-research.
• Writing or revising the feature design — use feature-design-doc.
• Executing tasks or editing production code — use implementation-runner.
• End-to-end orchestration — recommend prd-workflow.

---

Workflow

Break the design into implementable tasks.

1. Read the design document thoroughly.

2. Generate docs/features/{feature-name}/tasks.md with:

   • Phases — group tasks into logical phases (e.g., backend, frontend, integration).
   • Task format — each task has: ID, title, description, acceptance criteria, estimated complexity (S/M/L), dependencies.
   • Ordering — tasks within a phase are ordered by dependency. Independent tasks are marked as parallelizable.
   • Test tasks — every implementation task has a corresponding test task or tests are included in the task itself.