generate-implementation-plan

You can convert a basic plan into an execution-ready guide by applying planning enrichment, which embeds context, verification steps, and code-review workflows. This generates multi-file output with intro.md and task-*.md files for deterministic execution.

Planning enrichment is the process of transforming a basic plan into a structured, multi-file document set. It automates task decomposition, context gathering, and test discovery, embedding per-task verification directly into the plan files.

You structure plans by generating task-*.md files under a docs/plans/ directory, embedding inline context and mandatory code-review checkpoints. This template-driven structure ensures each task includes specific verification steps.

Yes, you can use asset-based templates to generate an indexed execution workflow. The process reads repository context and references, updates docs/plans/INDEX.md, and provides an execution handoff outline for fresh sessions.

You need to generate a multi-file plan after defining a feature plan or when preparing plans for fresh sessions. This enriches the original plan with automated task decomposition and reproducible checkpoints to enable automated execution.