create-implementation-plan

Generate executable implementation plans with phases, tasks, and validation criteria.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/angryconsultant/Copilot-CLI --skill create-implementation-plan-angryconsultant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-implementation-plan
Source: https://github.com/angryconsultant/Copilot-CLI/tree/main/skills/create-implementation-plan
Command: npx skills add https://github.com/angryconsultant/Copilot-CLI --skill create-implementation-plan-angryconsultant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of detailed, executable implementation plans for feature development, refactoring, or upgrades.

Core Features & Use Cases

  • Plan generation with clearly defined phases and tasks
  • Deterministic structure including required file paths, functions, and references
  • Automatic validation of plan completeness and naming conventions
  • Use Case: When starting a new feature, generate a complete plan that specifies steps, files, and validation criteria

Quick Start

Create an implementation plan for the specified PlanPurpose.

Frequently Asked Questions about create-implementation-plan

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

FAQPage Schema
How do I generate an executable implementation plan for feature development?

An implementation plan for feature development is generated by defining a PlanPurpose, which produces discrete phases, concrete tasks with exact file paths, and validation criteria in a machine-parseable format.

What is a deterministic implementation plan in project management?

A deterministic implementation plan is a machine-parseable project management format that enforces standardized naming conventions and requires exact file paths, functions, and references for all tasks.

Can I use this automation to plan refactoring tasks with specific file paths?

Yes, you can use this automation to plan refactoring tasks because it generates concrete tasks with exact file paths, function references, and validation criteria across all plan sections.

How do I create a plan that includes validation criteria for architecture upgrades?

To create a plan with validation criteria for architecture upgrades, specify the upgrade as the PlanPurpose, and the generated plan will enforce completeness with validation criteria across all sections.

What's the best way to structure implementation plans for automated workflows?

The best way to structure implementation plans for automated workflows is using a deterministic, machine-parseable format that saves plans under a standardized /plan directory with enforced naming conventions.

Do I need to manually specify file paths and functions when generating a project plan?

No, you do not need to manually specify file paths and functions when generating a project plan; the automation defines concrete tasks with exact references and validation criteria automatically.