create-implementation-plan

To generate an executable implementation plan, define the feature specification and target component. The plan creates a deterministic Markdown file with phase-based tasks, measurable completion criteria, and required dependencies for AI agents.

Breaking down a refactoring effort requires structuring work into discrete phases with atomic, parallelizable tasks. The resulting Markdown plan includes steps, alternatives, dependencies, and risks to ensure execution occurs without guesswork.

Yes, you can use a strict Markdown template for AI-parsable task breakdowns. The template enforces required frontmatter fields and mandated sections, saving plans to /plan/ using the [purpose]-[component]-[version].md naming convention.

Structuring an architecture upgrade plan involves generating a file with deterministic phase and task breakdowns. The plan specifies measurable completion criteria, required files, testing protocols, and risk mitigations to guide infrastructure changes.

Implementation planning requires no external dependencies or specific components to function. You only need to provide the PlanPurpose input, including relevant component or upgrade details, to generate the structured Markdown file.

You should not use a deterministic plan file for vague or exploratory tasks lacking measurable completion criteria. The strict Markdown template and atomic task breakdowns are designed for defined features, refactors, or architecture efforts requiring deterministic execution.