| name | implementation-plan-generation-mode |
| description | Generate fully executable implementation plans for new features, refactors, or architecture changes. Use when asked to plan, design phases, break down tasks, or create a roadmap. Produces machine-readable plans with atomic tasks, completion criteria, and zero ambiguity for autonomous AI or human execution. |
| argument-hint | [feature or refactor to plan] |
Implementation Plan Generation Mode
Generate implementation plans that are fully executable by AI agents or humans using deterministic language and explicit task structure.
Core Requirements
- Generate 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 — no external dependencies for understanding
Plan Structure
Plans consist of discrete, atomic phases containing executable tasks. Each phase must be independently processable.
- Each phase has measurable completion criteria
- Tasks within phases may run in parallel unless dependencies are declared
- All task descriptions include specific file paths, function names, and exact implementation details
- No task requires human interpretation or decision-making
AI-Optimised Standards
- Use explicit, unambiguous language with zero interpretation required
- Structure 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 standardised prefixes:
REQ-, TASK-, RISK-, FILE-, TEST-
- Include validation criteria that can be automatically verified
Output File Specification
- Save plans in
/plan/ directory
- Naming:
[purpose]-[component]-[version].md
- Purpose prefixes:
upgrade|refactor|feature|data|infrastructure|process|architecture|design
- Example:
feature-tag-editor-1.md, refactor-metadata-engine-2.md
Mandatory Template Structure
---
goal: [Concise Title]
version: 1.0
date_created: YYYY-MM-DD
status: 'Planned'
tags: [feature, refactor, etc.]
---
# Introduction
## 1. Requirements & Constraints
- **REQ-001**: Requirement
## 2. Implementation Steps
### Phase 1 — [Goal]
| Task | Description | Completed | Date |
|------|-------------|-----------|------|
| TASK-001 | ... | | |
## 3. Alternatives
## 4. Dependencies
## 5. Files Affected
## 6. Testing
## 7. Risks & Assumptions
When To Use This Skill
Invoke when the user asks to:
- "Plan the implementation of..."
- "Create a roadmap for..."
- "Break down the tasks for..."
- "Generate a phased plan for..."
