creating-implementation-plan

Generate a plan.md with phased implementation steps and REQ traceability checkpoints.

35|8|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/microsoft/github-copilot-modernization --skill creating-implementation-plan-microsoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-implementation-plan
Source: https://github.com/microsoft/github-copilot-modernization/tree/main/plugins/github-copilot-modernization/skills/creating-implementation-plan
Command: npx skills add https://github.com/microsoft/github-copilot-modernization --skill creating-implementation-plan-microsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a feature spec into a complete implementation plan and task decomposition, ensuring every requirement maps to concrete work items and traceable checkpoints.

Core Features & Use Cases

  • Generates a plan.md with phased implementation steps and REQ traceability.
  • Produces CHECKPOINT artifacts: spec-to-plan, plan-to-tasks, and requirement mapping.
  • Facilitates governance by mapping plan items to requirements and project topology if present.

Quick Start

Use this skill to generate a complete implementation plan and task breakdown from the feature spec and design artifacts, producing plan.md and checkpoints.

Frequently Asked Questions about creating-implementation-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an implementation plan from a feature spec?

Create an implementation plan by reading your feature spec and design artifacts to generate a plan.md with phased steps, task decomposition, and requirement traceability. It maps every requirement to concrete work items and checkpoints.

How do I decompose implementation tasks and ensure requirement traceability?

Decompose tasks and ensure traceability by mapping plan items to requirements via generated CHECKPOINT artifacts. These checkpoints validate spec-to-plan and plan-to-tasks mapping within a single repeatable workflow.

Can I use this to plan migrations as well as new feature implementation?

Yes, you can use this to plan migrations as well as new features. It reads design artifacts, policies, and dependencies to map requirements to actionable tasks for both scenarios.

What is the best way to map project topology and requirements to actionable tasks?

The best way to map topology and requirements to tasks is using a workflow that embeds REQ mappings and checkpoint generation, facilitating governance by connecting plan items directly to requirements and project topology if present.

Do I need design artifacts and policies to generate a task breakdown?

You need design artifacts, policies, and dependencies to generate a complete task breakdown. The process reads these inputs to enforce provenance and ensure every requirement maps to concrete work items and traceable checkpoints.