writing-plans

To turn feature requirements into an implementation plan, this skill translates specs into a comprehensive, task-by-task structure with bite-sized steps, exact file paths, and code examples to guide development.

Task breakdown for multi-step development workflows deconstructs complex features into discrete, executable milestones with explicit dependencies, acceptance criteria, and review checkpoints to reduce ambiguity and rework.

Generating documentation templates for design docs and tests is handled by enforcing a plan structure that includes guidance for tests, reviews, and handoff artifacts alongside concrete code examples.

Yes, this planning skill works for coordinating work across subagents by drafting comprehensive implementation plans that define precise task-by-task steps and milestones for distributed execution.

You need an implementation plan for software design when documenting complex projects or multi-step workflows before implementing features, ensuring requirements are broken down into concrete tasks with explicit file paths.

The best way to structure TDD documentation is using a plan template that enforces task-by-task steps with exact file paths, code examples, tests, and review checkpoints per feature requirement.