create-implementation-plan

To generate a machine-readable implementation plan for a software refactor, use this skill to produce deterministic, phase-based Markdown files with explicit file paths, identifiers, and validation criteria. It outputs structured plans ready for AI or human execution without extra interpretation.

A deterministic implementation plan for AI agents is a structured template featuring atomic phases, TASK identifiers, and measurable completion criteria. This skill creates these strict Markdown files to eliminate ambiguity during automated software engineering tasks like migrations.

Yes, you can create phased rollout plans for infrastructure migrations. The skill generates parallelizable, atomic tasks with explicit REQ identifiers and front matter status fields, ensuring infrastructure changes are mapped to exact file paths and automated validation steps.

The generated project plan does include specific file paths and function names. It enforces strict template rules and front matter validation, capturing exact identifiers and phase completion criteria required for reproducible feature development and architecture changes.

The best way to structure implementation plans for automated validation is using strict Markdown front matter and naming conventions. This skill enforces those output rules, generating phase-based templates with measurable criteria that automated tools can discover and validate.

You need an atomic implementation plan template for feature development when executing complex workflows requiring phased tasks. It suits scenarios like dependency upgrades or core module refactors where AI agents require explicit identifiers and strict validation rules to proceed accurately.