writing-plans

Generate an implementation plan by processing a feature spec to produce step-by-step tasks, required file references, testing strategies, and commit checkpoints. The plan is saved as a markdown file in the docs/plans directory to guide the entire coding workflow.

Breaking down complex software features into deterministic milestones requires structuring work into bite-sized tasks with explicit goals and test guidance. This approach documents acceptance criteria and enforces TDD principles to ensure clear, repeatable review steps.

Enforce TDD and DRY principles during software engineering task planning by documenting explicit testing strategies and acceptance criteria within the generated plan. This ensures engineers write tests and avoid duplication before coding begins.

Yes, you can use a commit-driven workflow in a dedicated worktree for feature implementation. The generated plan structures work into bite-sized tasks with commit checkpoints, ensuring deterministic milestones and clear review steps.

Yes, you need a feature spec to start planning software implementation steps. The plan generation solves the problem of starting from ambiguity by transforming the feature spec into explicit file references, tests, and documentation updates.

Avoid using automated step-by-step task breakdown for software projects that do not require structured task decomposition or deterministic milestones. It is designed for complex tasks needing explicit file references, testing strategies, and commit-driven workflows.