AgentSkillsCN

create-implementation-plan

为功能开发、重构、软件包升级、设计变更、架构决策，或基础设施改造，创建全新的实施计划文件。将结构化的Markdown计划保存至/plan/目录，其中包含阶段、任务、依赖关系、测试标准与风险分析。当用户说“制定计划”“撰写计划文件”或“为X生成实施计划”时使用。

SKILL.md
--- frontmatter
name: create-implementation-plan
description: Create a new implementation plan file for features, refactors, package upgrades, design changes, architecture decisions, or infrastructure work. Saves a structured Markdown plan to the /plan/ directory with phases, tasks, dependencies, test criteria, and risk analysis. Use when the user says "create a plan", "write a plan file", or "generate an implementation plan for X".
argument-hint: "[purpose of plan, e.g. 'advanced tag editor feature']"

Create Implementation Plan

Create machine-readable implementation plans with phases, tasks, dependencies, files, tests, and risks using deterministic language.

Primary Directive

Create a new implementation plan file for ${input:PlanPurpose}. Output must be machine-readable, deterministic, and structured for autonomous execution by other AI systems or humans.

Execution Context

All instructions must be interpreted literally and executed systematically without human interpretation or clarification.

Plan File Output Rules

  • •Save in /plan/ directory
  • •Naming: [purpose]-[component]-[version].md
  • •Valid purpose prefixes: upgrade | refactor | feature | data | infrastructure | process | architecture | design
  • •Examples: feature-tag-editor-1.md, refactor-metadata-engine-2.md

Template — Copy Exactly

markdown
---
goal: [Concise Title Describing the Plan Goal]
version: 1.0
date_created: YYYY-MM-DD
last_updated: YYYY-MM-DD
owner: [Team/Individual]
status: 'Planned'
tags: [feature, upgrade, chore, architecture, migration, bug]
---

# Introduction

![Status: Planned](https://img.shields.io/badge/status-Planned-blue)

[A short concise introduction to the plan and the goal it is intended to achieve.]

## 1. Requirements & Constraints

- **REQ-001**: Requirement 1
- **SEC-001**: Security Requirement 1
- **CON-001**: Constraint 1
- **GUD-001**: Guideline 1

## 2. Implementation Steps

### Implementation Phase 1 — [Phase Goal]

- GOAL-001: [Describe the goal of this phase]

| Task | Description | Completed | Date |
|------|-------------|-----------|------|
| TASK-001 | Description of task 1 | | |
| TASK-002 | Description of task 2 | | |

### Implementation Phase 2 — [Phase Goal]

- GOAL-002: [Describe the goal of this phase]

| Task | Description | Completed | Date |
|------|-------------|-----------|------|
| TASK-003 | Description of task 3 | | |

## 3. Alternatives

- **ALT-001**: Alternative approach and why not chosen

## 4. Dependencies

- **DEP-001**: Dependency description

## 5. Files Affected

- **FILE-001**: `path/to/file.py` — description of changes

## 6. Testing

- **TEST-001**: What to test and how

## 7. Risks & Assumptions

- **RISK-001**: Risk description and mitigation
- **ASSUMPTION-001**: Assumption description

Template Validation Rules

  • •All front matter fields must be present and properly formatted
  • •All section headers must match exactly (case-sensitive)
  • •All identifier prefixes must follow the specified format
  • •Tables must include all required columns
  • •No placeholder text may remain in the final output