Writing Plans

To generate an implementation plan for feature development with zero codebase context, use a skill that produces bite-sized tasks detailing exact file paths, concrete commands, tests, and commit guidance. It saves the plan to docs/plans/YYYY-MM-DD-<feature-name>.md.

To break down software engineering designs into bite-sized tasks for TDD workflows, generate structured plan documentation that emphasizes DRY, YAGNI, and test-driven development. It outlines every step, touchpoint, test, and documentation needed across multiple files.

Planning a feature with this approach does require a dedicated worktree, which is announced at the start. It ensures that the end-to-end implementation plan detailing steps, touchpoints, and commits is executed in an isolated environment.

The best way to document task breakdowns for engineers across multiple files is to save comprehensive plans to a dedicated markdown file. It produces bite-sized tasks with file paths, code, tests, and commit guidance for engineers needing exact implementation steps.

You can use this implementation plan generation for codegen workflows requiring exact file paths, concrete commands, and structured plan documentation. It satisfies requirements for explicit task breakdowns, tests, docs, and commits across multiple files.