create-implementation-plan

To generate a deterministic implementation plan for software refactoring, provide a refactor request and the tool outputs a machine-readable Markdown file with structured phases, requirements, constraints, and validation criteria.

A machine-readable phased implementation plan is a structured Markdown document using explicit REQ-/TASK-/DEP-/TEST- identifiers that breaks work into independently processable phases with measurable completion criteria for automated parsing.

You create an implementation plan for an infrastructure upgrade request by submitting the request to be processed into a strict mandatory template with deterministic language constraints, saving the output file under the /plan/ directory.

Yes, you can use this implementation plan generator without external dependencies because it ensures no external dependencies are needed for understanding the structured phased plan with requirements, constraints, tasks, and validation criteria.

The best way to structure task breakdown for architecture documentation is applying a strict mandatory plan template with required front matter fields, yielding deterministic Markdown files with explicit identifiers under the /plan/ directory.

Your implementation plan requires explicit validation criteria and risk items because it is validation-oriented planning, forcing dependencies, testing items, and assumptions so execution can be verified without ambiguity by other agents or humans.