create-implementation-plan

Generate structured implementation plan Markdown files for features, refactoring, and upgrades.

25|4|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/thangchung/agent-engineering-experiment --skill create-implementation-plan-thangchung
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-implementation-plan
Source: https://github.com/thangchung/agent-engineering-experiment/tree/main/agentgateway-entraid-obo/.claude/skills/create-implementation-plan
Command: npx skills add https://github.com/thangchung/agent-engineering-experiment --skill create-implementation-plan-thangchung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing implementation plans that both humans and AI agents can execute consistently is hard—plans often lack structure, contain ambiguous tasks, or use duplicate identifiers that break automated parsing. This Skill produces deterministic, machine-readable implementation plan files with a strict template and validation rules. ## Core Features & Use Cases - Standardized Plan Template: Enforces a mandatory Markdown structure with front matter, requirements, phased tasks, dependencies, risks, and testing sections. - Unique Identifier System: Uses prefixed identifiers (REQ-, TASK-, GOAL-, DEP-, etc.) with shell-based validation checks to guarantee each identifier is declared exactly once. - AI-Executable Output: Tasks include specific file paths, function names, and measurable completion criteria so autonomous agents can execute phases without human interpretation. - Use Case: When planning a package upgrade or new feature, ask for an implementation plan and receive a /plan/upgrade-auth-module-1.md file with phased task tables, status badges, and verifiable completion criteria. ## Quick Start Create an implementation plan for upgrading the authentication module to support OAuth2 token refresh.

Frequently Asked Questions about create-implementation-plan

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

FAQPage Schema
How do I create an implementation plan for a new feature?▼

Invoke the Skill with the plan purpose, such as a feature or upgrade. It generates a Markdown file in the /plan/ directory following the naming convention [purpose]-[component]-[version].md, with phased tasks, requirements, and validation criteria.

What is the implementation plan file naming convention?▼

Plan files use the pattern [purpose]-[component]-[version].md, where purpose is one of upgrade, refactor, feature, data, infrastructure, process, architecture, or design. Example: feature-auth-module-1.md.

How do I validate unique identifiers in an implementation plan?▼

Run the provided grep, sed, sort, and uniq shell commands against the plan file to detect duplicate TASK, GOAL, REQ, and other prefixed identifier declarations. Checks one and two must return zero rows before finalizing.

Does the plan validation work on Windows?▼

The validation commands require a POSIX-compatible shell with grep, sed, sort, and uniq. On Windows without these tools, use equivalent platform-native commands while preserving the same declaration-versus-reference logic.

What status values can an implementation plan have?▼

Plans support five status values in the front matter: Completed, In progress, Planned, Deprecated, and On Hold. Each status also appears as a colored badge in the introduction section.