writing-plans

To break down complex software work, generate a step-by-step implementation plan that specifies clear tasks, files to touch, tests to run, and expected outputs across multiple steps, breaking work into small verifiable actions.

The best way to document requirements before coding is to create a formal plan document outlining step-by-step tasks with clear acceptance criteria, embracing DRY, YAGNI, and TDD philosophies to reduce ambiguity and rework.

You create a TDD implementation plan by documenting each task with specific file touch details, test commands to run, and expected outputs, saving the formal plan document to guide subagents during development.

You should save implementation plans for multi-step software development tasks to a markdown file at docs/plans/YYYY-MM-DD-<feature-name>.md, ensuring the plan includes a feature-branch name to guide subagents.

Planning multi-step tasks before coding reduces rework by creating comprehensive, executable plans that target specifications with clear tasks, test commands, and expected outputs, enabling teams to verify small actions before committing.

Yes, you can use a structured implementation plan to guide subagents by providing a formal document with file touch details, test commands, expected outputs, and a feature-branch name for clear direction.