writing-plans

To turn a feature spec into a test-driven implementation plan, you provide the written requirements to generate bite-sized TDD steps. The output includes exact file paths, failing test templates, minimal implementations, and commit instructions saved to docs/plans/YYYY-MM-DD-<feature-name>.md.

The best way to break down multi-step engineering tasks is by generating a standardized plan header and explicit step-by-step instructions. This approach removes ambiguity by detailing which files to change, what tests to write, and expected command outputs for quick handoffs.

To generate failing test templates and commit instructions for TDD workflow changes, the plan output prescribes exact test file locations, commands to run tests, and minimal implementations for each incremental task. This ensures disciplined feature development and reliable validation.

Yes, you can use this implementation plan approach for small-to-medium codebase tasks and contractor onboarding. It produces exact file and command guidance with expected outputs, enabling quick handoffs for engineers who have no prior context about the codebase.

Yes, the generated implementation plan includes exact file paths and commands to run tests. It provides create/modify file locations, test file directories, expected command outputs, and explicit commit steps to validate each incremental change.

You need a prescribed plan header saved to docs/plans when starting feature development or TDD-driven changes. It standardizes the goal, architecture, and tech stack, ensuring engineers with no context can follow explicit step-by-step instructions reliably.