create-implementation-plan by github/awesome-copilot
npx skills add https://github.com/github/awesome-copilot --skill create-implementation-plan你的目标是为 ${input:PlanPurpose} 创建一个新的实施方案文件。你的输出必须是机器可读的、确定性的,并且结构化为可供其他 AI 系统或人类自主执行。
此提示专为 AI 间通信和自动化处理而设计。所有指令必须按字面意思解释并系统性地执行,无需人工解释或澄清。
计划必须由包含可执行任务的离散、原子化阶段组成。每个阶段必须能够由 AI 代理或人类独立处理,除非明确声明,否则不存在跨阶段依赖。
/plan/ 目录中[purpose]-[component]-[version].md广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
upgrade|refactor|feature|data|infrastructure|process|architecture|designupgrade-system-command-4.md, feature-auth-module-1.md所有实施方案必须严格遵循以下模板。每个部分都是必需的,并且必须填充具体的、可操作的内容。AI 代理在执行前必须验证模板合规性。
实施方案的状态必须在 front matter 中明确定义,并且必须反映计划的当前状态。状态可以是以下之一(括号内为 status_color):Completed(亮绿色徽章)、In progress(黄色徽章)、Planned(蓝色徽章)、Deprecated(红色徽章)或 On Hold(橙色徽章)。它也应在介绍部分显示为徽章。
---
goal: [描述包实施方案目标的简明标题]
version: [可选:例如,1.0, 日期]
date_created: [YYYY-MM-DD]
last_updated: [可选:YYYY-MM-DD]
owner: [可选:负责此规范的团队/个人]
status: 'Completed'|'In progress'|'Planned'|'Deprecated'|'On Hold'
tags: [可选:相关标签或类别的列表,例如 `feature`, `upgrade`, `chore`, `architecture`, `migration`, `bug` 等]
---
# 介绍

[对计划及其旨在实现的目标的简短介绍。]
## 1. 需求与约束
[明确列出所有影响计划并约束其实现方式的需求和约束。为清晰起见,使用项目符号或表格。]
- **REQ-001**: 需求 1
- **SEC-001**: 安全需求 1
- **[3 LETTERS]-001**: 其他需求 1
- **CON-001**: 约束 1
- **GUD-001**: 指南 1
- **PAT-001**: 要遵循的模式 1
## 2. 实施步骤
### 实施阶段 1
- GOAL-001: [描述此阶段的目标,例如“实现功能 X”、“重构模块 Y”等。]
| 任务 | 描述 | 已完成 | 日期 |
|------|-------------|-----------|------|
| TASK-001 | 任务 1 的描述 | ✅ | 2025-04-25 |
| TASK-002 | 任务 2 的描述 | | |
| TASK-003 | 任务 3 的描述 | | |
### 实施阶段 2
- GOAL-002: [描述此阶段的目标,例如“实现功能 X”、“重构模块 Y”等。]
| 任务 | 描述 | 已完成 | 日期 |
|------|-------------|-----------|------|
| TASK-004 | 任务 4 的描述 | | |
| TASK-005 | 任务 5 的描述 | | |
| TASK-006 | 任务 6 的描述 | | |
## 3. 备选方案
[任何已考虑但未被选中的替代方法的项目符号列表。这有助于为所选方法提供背景和理由。]
- **ALT-001**: 替代方法 1
- **ALT-002**: 替代方法 2
## 4. 依赖项
[列出需要解决的任何依赖项,例如计划所依赖的库、框架或其他组件。]
- **DEP-001**: 依赖项 1
- **DEP-002**: 依赖项 2
## 5. 文件
[列出将受功能或重构任务影响的所有文件。]
- **FILE-001**: 文件 1 的描述
- **FILE-002**: 文件 2 的描述
## 6. 测试
[列出需要实施的测试,以验证功能或重构任务。]
- **TEST-001**: 测试 1 的描述
- **TEST-002**: 测试 2 的描述
## 7. 风险与假设
[列出与计划实施相关的任何风险或假设。]
- **RISK-001**: 风险 1
- **ASSUMPTION-001**: 假设 1
## 8. 相关规范 / 延伸阅读
[链接到相关规范 1]
[链接到相关外部文档]
每周安装量
7.6K
代码仓库
GitHub 星标数
26.7K
首次出现
2026年2月25日
安全审计
安装于
codex7.5K
gemini-cli7.4K
opencode7.4K
github-copilot7.4K
cursor7.4K
kimi-cli7.4K
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.
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.
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.
/plan/ directory[purpose]-[component]-[version].mdupgrade|refactor|feature|data|infrastructure|process|architecture|designupgrade-system-command-4.md, feature-auth-module-1.mdAll implementation plans must strictly adhere to the following template. Each section is required and must be populated with specific, actionable content. AI agents must validate template compliance before execution.
The status of the implementation plan must be clearly defined in the front matter and must reflect the current state of the plan. The status can be one of the following (status_color in brackets): Completed (bright green badge), In progress (yellow badge), Planned (blue badge), Deprecated (red badge), or On Hold (orange badge). It should also be displayed as a badge in the introduction section.
---
goal: [Concise Title Describing the Package Implementation Plan's Goal]
version: [Optional: e.g., 1.0, Date]
date_created: [YYYY-MM-DD]
last_updated: [Optional: YYYY-MM-DD]
owner: [Optional: Team/Individual responsible for this spec]
status: 'Completed'|'In progress'|'Planned'|'Deprecated'|'On Hold'
tags: [Optional: List of relevant tags or categories, e.g., `feature`, `upgrade`, `chore`, `architecture`, `migration`, `bug` etc]
---
# Introduction

[A short concise introduction to the plan and the goal it is intended to achieve.]
## 1. Requirements & Constraints
[Explicitly list all requirements & constraints that affect the plan and constrain how it is implemented. Use bullet points or tables for clarity.]
- **REQ-001**: Requirement 1
- **SEC-001**: Security Requirement 1
- **[3 LETTERS]-001**: Other Requirement 1
- **CON-001**: Constraint 1
- **GUD-001**: Guideline 1
- **PAT-001**: Pattern to follow 1
## 2. Implementation Steps
### Implementation Phase 1
- GOAL-001: [Describe the goal of this phase, e.g., "Implement feature X", "Refactor module Y", etc.]
| Task | Description | Completed | Date |
|------|-------------|-----------|------|
| TASK-001 | Description of task 1 | ✅ | 2025-04-25 |
| TASK-002 | Description of task 2 | | |
| TASK-003 | Description of task 3 | | |
### Implementation Phase 2
- GOAL-002: [Describe the goal of this phase, e.g., "Implement feature X", "Refactor module Y", etc.]
| Task | Description | Completed | Date |
|------|-------------|-----------|------|
| TASK-004 | Description of task 4 | | |
| TASK-005 | Description of task 5 | | |
| TASK-006 | Description of task 6 | | |
## 3. Alternatives
[A bullet point list of any alternative approaches that were considered and why they were not chosen. This helps to provide context and rationale for the chosen approach.]
- **ALT-001**: Alternative approach 1
- **ALT-002**: Alternative approach 2
## 4. Dependencies
[List any dependencies that need to be addressed, such as libraries, frameworks, or other components that the plan relies on.]
- **DEP-001**: Dependency 1
- **DEP-002**: Dependency 2
## 5. Files
[List the files that will be affected by the feature or refactoring task.]
- **FILE-001**: Description of file 1
- **FILE-002**: Description of file 2
## 6. Testing
[List the tests that need to be implemented to verify the feature or refactoring task.]
- **TEST-001**: Description of test 1
- **TEST-002**: Description of test 2
## 7. Risks & Assumptions
[List any risks or assumptions related to the implementation of the plan.]
- **RISK-001**: Risk 1
- **ASSUMPTION-001**: Assumption 1
## 8. Related Specifications / Further Reading
[Link to related spec 1]
[Link to relevant external documentation]
Weekly Installs
7.6K
Repository
GitHub Stars
26.7K
First Seen
Feb 25, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykFail
Installed on
codex7.5K
gemini-cli7.4K
opencode7.4K
github-copilot7.4K
cursor7.4K
kimi-cli7.4K
97,600 周安装