write-plans

To convert an approved design into an execution plan, provide the design or requirements document to generate a structured task list. This process maps the design into manageable steps with explicit file touches, tests, documentation, and commit-ready actions.

Task decomposition for multi-step changes is the process of breaking down approved designs into independent, deployable task sets. It structures work into manageable steps with owners, milestones, acceptance criteria, and specific file modifications.

You can generate a task plan with file touches, tests, and documentation by submitting your approved requirements. The output produces a detailed plan document saved to changes/<change-id>/tasks.md, containing structured steps for engineering execution.

Yes, task decomposition applies to projects involving multiple subsystems by generating independent, deployable task sets that align with the overall design. This ensures each subsystem receives explicit steps for tests, documentation, and file modifications.

The best way to transition from design specs to development handoff is converting approved requirements into clear, executable task plans. This reduces ambiguity by defining explicit file touches, acceptance criteria, and commit-ready steps for faster engineering execution.

Yes, you need an approved design or requirements document to generate an execution plan. The skill translates existing specifications into actionable task-by-task plans, requiring completed design inputs to produce accurate file touches and acceptance criteria.