writing-plans

To turn a feature specification into a TDD implementation plan, provide your requirements to generate a structured, bite-sized task list. The output includes failing tests, exact file paths, run commands, and commit steps saved as a dated markdown file with matching native tasks.

The best way to break multi-step engineering work into bite-sized tasks is using a TDD-first workflow that segments features into 2–5 minute actionable steps. Each step cycles through writing a failing test, running it, implementing minimal code, and committing.

Native task tracking integrates with implementation plans by creating linked tasks with blockedBy relationships and a co-located .tasks.json file. This setup allows you to resume execution seamlessly across sessions while maintaining dependency awareness.

Yes, a dedicated worktree is required for this implementation planning workflow. The process assumes a worktree-first approach to isolate changes, enforce test-driven development checkpoints, and maintain exact commit guidance throughout the feature build.

Yes, you can save implementation plans as markdown files in your repository. The process automatically generates a saved docs/plans/YYYY-MM-DD-feature.md file containing the full structured task breakdown, file paths, and execution handoff details.

A limitation when generating TDD-style tasks is that the execution handoff is constrained to an AskUserQuestion mechanism for choice selection. Additionally, the workflow strictly enforces frequent checkpoints and minimal code implementation, which may not suit non-test-driven development environments.