Back to Details

create-plan

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Create Implementation Plan

创建实施计划

Generate comprehensive implementation plans that provide strategic guidance without making actual code changes.
生成提供战略指导但不进行实际代码修改的全面实施计划。

When to Use

适用场景

  • User explicitly requests a plan, roadmap, or implementation strategy
  • Complex tasks requiring structured breakdown before implementation
  • Need for risk assessment and alternative approach analysis
  • Pre-implementation analysis of architectural decisions
  • 用户明确要求提供计划、路线图或实施策略
  • 需要在实施前进行结构化拆解的复杂任务
  • 需要进行风险评估和备选方案分析的场景
  • 架构决策的实施前分析

Planning Process

规划流程

1. Initial Assessment

1. 初始评估

Research the codebase to understand:
  • Project structure and organization
  • Relevant files and components
  • Existing patterns and conventions
  • Potential challenges and risks
Use 
search
and 
read
tools to examine the codebase. Use 
sage
if deeper research is required for the use-case. Explicitly cite sources using 
filepath:line
format.
研究代码库以了解：
  • 项目结构与组织方式
  • 相关文件与组件
  • 现有模式与规范
  • 潜在挑战与风险
使用
search
和
read
工具检查代码库。如果针对该用例需要更深入的研究，可使用
sage
工具。需使用
filepath:line
格式明确引用来源。

2. Create Strategic Plan

2. 创建战略计划

Generate a Markdown plan file in 
plans/
directory with naming: 
plans/{YYYY-MM-DD}-{task-name}-v{N}.md
Example: 
plans/2025-11-24-add-auth-v1.md
在
plans/
目录下生成Markdown计划文件，命名格式为：
plans/{YYYY-MM-DD}-{task-name}-v{N}.md
示例：
plans/2025-11-24-add-auth-v1.md

3. Validate Plan

3. 验证计划

MANDATORY: Run the validation script to ensure the plan meets all requirements:
bash
./.forge/skills/create-plan/validate-plan.sh plans/{YYYY-MM-DD}-{task-name}-v{N}.md
Fix any errors or warnings and re-validate until the plan passes all checks.
强制要求： 运行验证脚本以确保计划符合所有要求：
bash
./.forge/skills/create-plan/validate-plan.sh plans/{YYYY-MM-DD}-{task-name}-v{N}.md
修复所有错误或警告，重新验证直到计划通过所有检查。

4. Plan Structure

4. 计划结构

markdown
undefined
markdown
undefined

[Task Name]

[任务名称]

Objective

目标

[Clear statement of goal and expected outcomes]
[清晰的目标与预期成果说明]

Implementation Plan

实施计划

  • 1. [First task with detailed description and rationale]
  • 2. [Second task with detailed description and rationale]
  • 3. [Third task with detailed description and rationale]
  • 1. [第一项任务，含详细描述与实施理由]
  • 2. [第二项任务，含详细描述与实施理由]
  • 3. [第三项任务，含详细描述与实施理由]

Verification Criteria

验证标准

  • [Criterion 1: Specific, measurable outcome]
  • [Criterion 2: Specific, measurable outcome]
  • [标准1：具体、可衡量的成果]
  • [标准2：具体、可衡量的成果]

Potential Risks and Mitigations

潜在风险与缓解措施

  1. [Risk Description] Mitigation: [Specific mitigation strategy]
  2. [Risk Description] Mitigation: [Specific mitigation strategy]
  1. [风险描述] 缓解措施：[具体的缓解策略]
  2. [风险描述] 缓解措施：[具体的缓解策略]

Alternative Approaches

备选方案

  1. [Alternative 1]: [Brief description and trade-offs]
  2. [Alternative 2]: [Brief description and trade-offs]
undefined
  1. [备选方案1]：[简要描述与利弊分析]
  2. [备选方案2]：[简要描述与利弊分析]
undefined

Critical Requirements

核心要求

  • ALWAYS validate the plan using 
    ./.forge/skills/create-plan/validate-plan.sh
    after creation
  • ALWAYS use checkbox format (
    - [ ]
    ) for ALL implementation tasks
  • NEVER use numbered lists or plain bullet points in Implementation Plan section
  • NEVER write code, code snippets, or code examples in the plan
  • Include clear rationale for each task
  • Provide specific, measurable verification criteria
  • Document assumptions made for ambiguous requirements
  • Focus on strategic "what" and "why", not tactical "how"
  • Describe what needs to be done using natural language, not code
  • 必须始终在创建后使用
    ./.forge/skills/create-plan/validate-plan.sh
    验证计划
  • 所有实施任务必须始终使用复选框格式(
    - [ ]
    )
  • 在实施计划部分绝对不能使用编号列表或普通项目符号
  • 绝对不能在计划中编写代码、代码片段或代码示例
  • 为每项任务添加清晰的实施理由
  • 提供具体、可衡量的验证标准
  • 记录针对模糊需求所做的假设
  • 聚焦于战略层面的“做什么”和“为什么”，而非战术层面的“怎么做”
  • 使用自然语言描述实施内容，而非代码

Best Practices

最佳实践

  • Make reasonable assumptions when requirements are ambiguous
  • Use codebase patterns to infer best practices
  • Provide multiple solution paths for complex challenges
  • Balance thoroughness with actionability
  • Create plans that can be executed step-by-step by implementation agents
  • 当需求模糊时做出合理假设
  • 利用代码库模式推导最佳实践
  • 为复杂挑战提供多种解决方案路径
  • 在全面性与可执行性之间取得平衡
  • 创建可由实施Agent逐步执行的计划

Boundaries

边界限制

This is a planning-only skill:
  • ✅ Research codebase and analyze structure
  • ✅ Create strategic plans and documentation
  • ✅ Assess risks and propose alternatives
  • ✅ Describe implementations using natural language
  • ❌ Make actual code changes
  • ❌ Modify files or create implementations
  • ❌ Run tests or build commands
  • ❌ Write code, code snippets, or code examples in plans
If user requests implementation work, suggest switching to an implementation agent.
这是一项仅专注于规划的技能：
  • ✅ 研究代码库并分析结构
  • ✅ 创建战略计划与文档
  • ✅ 评估风险并提出备选方案
  • ✅ 使用自然语言描述实施内容
  • ❌ 进行实际代码修改
  • ❌ 修改文件或创建实现
  • ❌ 运行测试或构建命令
  • ❌ 在计划中编写代码、代码片段或代码示例
如果用户要求实施工作，建议切换到实施Agent。