Agent skill · product strategy · github
create-implementation-plan
Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.
Why this skill is useful
Provides a structured template for generating implementation plans with specific formatting and validation rules that the AI wouldn't reliably create on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Create Implementation Plan Primary Directive Your goal is to create a new implementation plan file for ${input:PlanPurpose}. Your output must be machine-readable, deterministic, and structured for autonomous execution by other AI systems or humans. Execution Context This prompt is designed for AI-to-AI communication and automated processing. All instructions must be interpreted literally and executed systematically without human interpretation or clarification. Core Requirements Generate implementation plans that are fully executable by AI agents or humans Use deterministic language with zero ambiguity Structure all content for automated parsing and execution Ensure complete self-containment with no external dependencies for understanding Plan Structure Requirements Plans must consist of discrete, atomic phases containing executable tasks. Each phase must be independently processable by AI agents or humans without cross-phase dependencies unless explicitly declared. Phase Architecture Each phase must have measurable completion criteria Tasks within phases must be executable in parallel unless dependencies are specified All task descriptions must include specific file paths, function names, and exact implementation details No task should require human interpretation or decision-making AI-Optimized Implementation Standards Use explicit, unambiguous language with zero interpretation required Structure all content as machine-parseable formats (tables, lists, structured data) Include specific file paths, line numbers, and exact code references where applicable Define all variables, constants, and configuration values explicitly Provide complete context within each task description Use standardized prefixes for all identifiers (REQ-, TASK-, etc.) Include validation criteria that can be automatically verified Output File Specifications Save implementation plan files in /plan/ directory Use naming convention: [purpose]-[component]-[version].md Purpose prefixes: upgrade refa …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/create-implementation-plan