writing-plans

To generate a multi-step implementation plan, you use a dedicated worktree where the feature details are processed into a structured markdown file. The resulting plan documents tasks, required files, testing strategies, and commit milestones.

Documenting task breakdowns for zero-context engineers requires specifying touched files, tests, docs, and commits in a standardized template. This provides a repeatable structure that standardizes handoffs and defines exact file-path references.

Automated planning handles execution handoffs by satisfying strict frontmatter and plan structure standards within the generated markdown. This ensures downstream agents receive named sub-sections and exact file-path references for seamless execution.

Yes, you need a dedicated worktree to plan complex software engineering tasks. The worktree isolates the planning process and stores the generated plans under the docs/plans directory using a YYYY-MM-DD feature name format.

The limitations of standardized implementation plans include strict adherence to frontmatter and named sub-sections. Plans are specifically structured for multi-step workflows requiring thorough planning and execution handoffs, which may not suit simple tasks.