create-implementation-plan

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

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/miyake-san/sogo-agent-platform --skill create-implementation-plan-miyake-san
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-implementation-plan
Source: https://github.com/miyake-san/sogo-agent-platform/tree/main/skills/core/create-implementation-plan
Command: npx skills add https://github.com/miyake-san/sogo-agent-platform --skill create-implementation-plan-miyake-san

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing implementation plans that both humans and AI agents can execute without ambiguity is difficult; this Skill produces deterministic, machine-readable plan documents with a strict, validated template. ## Core Features & Use Cases - Standardized Plan Template: Enforces a mandatory Markdown structure with front matter, requirements, phased tasks, dependencies, risks, and testing sections. - AI-Optimized Output: Uses atomic phases, standardized identifier prefixes (REQ-, TASK-, GOAL-), and explicit file paths so plans can be executed autonomously by AI agents. - Naming & Status Conventions: Saves plans to /plan/ with purpose-prefixed filenames (e.g., feature-auth-module-1.md) and status badges (Planned, In progress, Completed, Deprecated, On Hold). - Use Case: When starting a package upgrade or new feature, ask the agent to produce a complete implementation plan that another agent can later execute phase by phase without further clarification. ## Quick Start Create an implementation plan for upgrading the authentication module to support OAuth2.

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 the feature name. It generates a Markdown file in the /plan/ directory following the mandatory template with requirements, phased tasks, dependencies, files, tests, and risks sections.

What is the naming convention for implementation plan files?

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.

What status values can an implementation plan have?

Plans support five statuses shown as badges: Completed, In progress, Planned, Deprecated, and On Hold. The status is set in the front matter and displayed as a badge in the introduction section.

Can AI agents execute the generated implementation plans?

Yes, plans are designed for AI-to-AI communication with atomic phases, explicit file paths, standardized identifiers like REQ-001 and TASK-001, and measurable completion criteria so agents can execute tasks without human interpretation.

What sections are mandatory in the plan template?

The template requires front matter, Introduction, Requirements & Constraints, Implementation Steps with phases, Alternatives, Dependencies, Files, Testing, Risks & Assumptions, and Related Specifications. All headers must match exactly and no placeholder text may remain.