create-implementation-plan

A machine-readable implementation plan provides deterministic, phase-based atomic tasks with explicit file paths, standardized identifiers, and validation criteria for automated agent execution. You need this format when automating feature development, architecture changes, refactoring tasks, or infrastructure upgrades without human interpretation.

To generate a structured implementation plan for refactoring, provide the target module details to produce phase-based atomic tasks with explicit file paths, standardized TASK- identifiers, tests to add, and measurable validation steps. This ensures deterministic, machine-parseable specifications for automated verification of the refactoring tasks.

Yes, you can generate deterministic, machine-readable plans for infrastructure upgrades and package migrations. The Skill produces phase-based plans with exact file paths to change, explicit completion criteria, and automated validation checks tailored for infrastructure work and deployments.

Yes, the generated implementation plan enforces templates with required Markdown front matter, standardized identifier prefixes like REQ-, explicit file paths, and validation rules for automated verification. These machine-parseable specifications ensure each atomic task has measurable completion criteria.

The best way to prepare machine-parseable specifications is to generate phase-based plans composed of atomic, independently executable tasks. This approach enforces required front matter, standardized identifier prefixes, explicit file paths, and validation rules, removing ambiguity for automated agent execution during software engineering tasks.