writing-plans

To generate a test-first implementation plan, provide a project specification and the workflow converts it into an executable plan with exact file paths, complete code blocks, and verification steps. The output is saved as a markdown file under docs/plans.

The best way to break down a feature is using a standardized plan structure with a header, task sections, and save-location conventions. This creates commit-ready steps with explicit checkpoints so engineers can work end-to-end without ambiguity.

Yes, you can apply test-driven development plans to multi-step development tasks across any codebase. The generated plan enforces a test-first workflow by including exact file paths for every operation alongside complete verification steps.

Yes, the generated implementation plan includes exact file paths for every operation and complete code blocks. It also provides verification steps that enable rapid, repeatable implementation for the development team.

You should save the implementation plan markdown file to the docs/plans directory using the YYYY-MM-DD-<feature-name>.md naming convention. This ensures plans are organized by date and feature for easy handoff.

You need an executable plan with verification steps when starting a new feature with a spec and handing it off to a development team. It ensures reliable, ready-to-execute implementation with explicit checkpoints for test-first workflows.