Back to Details

project-planner

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Project Planner Skill

Project Planner Skill

Universal planning methodology for creating structured, actionable plans for any project type. Works for business initiatives, personal goals, creative projects, academic work, event planning, and organizational change.
适用于所有项目类型的通用规划方法论，可创建结构化、可执行的计划。支持商业举措、个人目标、创意项目、学术工作、活动策划和组织变革等场景。

When to Use This Skill

何时使用此技能

Activate this skill when planning:
  • Business Projects: Product launches, marketing campaigns, process improvements
  • Personal Goals: Career development, learning objectives, lifestyle changes
  • Creative Projects: Writing projects, art installations, content creation
  • Academic Work: Research projects, thesis planning, study programs
  • Event Planning: Conferences, weddings, community events
  • Organizational Change: Restructuring, culture initiatives, policy changes
NOT for software development - Use 
implementation-planner
skill instead
在规划以下项目时激活此技能：
  • 商业项目：产品发布、营销活动、流程优化
  • 个人目标：职业发展、学习目标、生活方式改变
  • 创意项目：写作项目、艺术装置、内容创作
  • 学术工作：研究项目、论文规划、学习方案
  • 活动策划：会议、婚礼、社区活动
  • 组织变革：团队重组、文化建设、政策调整
不适用于软件开发 - 请改用
implementation-planner
技能

Pre-Planning Protocol

预规划流程

ALWAYS execute before creating new plan:
  1. Check for active plan:
    bash
    test -f docs/plan.md && cat docs/plan.md
  2. If active plan exists:
    • Ask user: "Active plan found: [PLAN-ID]. Continue this plan or create new one?"
    • If continue: Load active plan and continue from current phase
    • If new: Mark current plan as paused/completed and create new
  3. If no active plan:
    • Proceed with new plan creation
创建新计划前必须执行以下步骤：
  1. 检查是否存在活跃计划：
    bash
    test -f docs/plan.md && cat docs/plan.md
  2. 若存在活跃计划：
    • 询问用户："检测到活跃计划：[PLAN-ID]。是继续此计划还是创建新计划？"
    • 若选择继续：加载活跃计划并从当前阶段推进
    • 若选择新建：将当前计划标记为暂停/完成，然后创建新计划
  3. 若不存在活跃计划：
    • 直接推进新计划创建

Plan Format Standards

计划格式标准

Naming Convention

命名规范

  • Format: 
    PLAN-YYYYMMDD-HHMM-{project-slug}.md
  • Example: 
    PLAN-20251118-1430-product-launch.md
  • Location: 
    docs/plans/
  • 格式：
    PLAN-YYYYMMDD-HHMM-{project-slug}.md
  • 示例：
    PLAN-20251118-1430-product-launch.md
  • 存储位置：
    docs/plans/

Required Frontmatter

必填前置元数据

yaml
---
plan_id: PLAN-YYYYMMDD-HHMM-{slug}
title: [Project Name]
created: YYYY-MM-DD HH:MM
status: draft | active | completed | on_hold | cancelled
category: business | personal | creative | academic | event | organizational
phase: planning | execution | monitoring | complete
priority: critical | high | medium | low
---
yaml
---
plan_id: PLAN-YYYYMMDD-HHMM-{slug}
title: [项目名称]
created: YYYY-MM-DD HH:MM
status: draft | active | completed | on_hold | cancelled
category: business | personal | creative | academic | event | organizational
phase: planning | execution | monitoring | complete
priority: critical | high | medium | low
---

Required Sections

必填章节

  1. Vision & Objectives - What and why
  2. Scope & Deliverables - Specific outcomes
  3. Action Steps - Sequenced tasks with owners
  4. Resources Required - People, budget, materials, time
  5. Timeline & Milestones - Deadlines and checkpoints
  6. Risks & Contingencies - What could go wrong
  7. Success Metrics - Measurable outcomes
  1. 愿景与目标 - 项目内容及意义
  2. 范围与交付成果 - 具体产出
  3. 行动步骤 - 明确责任人的有序任务
  4. 所需资源 - 人员、预算、物料、时间
  5. 时间线与里程碑 - 截止日期与检查点
  6. 风险与应急预案 - 潜在问题及应对方案
  7. 成功指标 - 可衡量的产出

Master Plan Tracker (docs/plan.md)

主计划跟踪器（docs/plan.md）

Same structure as implementation-planner, tracks all project plans.
与
implementation-planner
结构一致，用于跟踪所有项目计划。

Update Workflow

更新工作流

When creating new plan:
  1. Generate plan file in 
    docs/plans/
  2. Update 
    docs/plan.md
    :
    • Set 
      active_plan
      to new plan ID
    • Add to appropriate category section
    • Update 
      last_updated
      timestamp
When completing plan:
  1. Update plan file 
    status: completed
  2. Update 
    docs/plan.md
    :
    • Move to "Completed" with ✅
    • Update statistics
When pausing plan:
  1. Update plan file 
    status: on_hold
  2. Update 
    docs/plan.md
    :
    • Move to "On Hold" section
    • Clear 
      active_plan
      if it was active
创建新计划时：
  1. 在
    docs/plans/
    目录下生成计划文件
  2. 更新
    docs/plan.md
    ：
    • 将
      active_plan
      设置为新计划ID
    • 添加至对应分类章节
    • 更新
      last_updated
      时间戳
完成计划时：
  1. 将计划文件的
    status
    更新为
    completed
  2. 更新
    docs/plan.md
    ：
    • 将计划移至“已完成”章节并标记✅
    • 更新统计数据
暂停计划时：
  1. 将计划文件的
    status
    更新为
    on_hold
  2. 更新
    docs/plan.md
    ：
    • 将计划移至“暂停”章节
    • 若该计划为活跃计划，清空
      active_plan
      字段

Core Planning Principles

核心规划原则

  1. Clarity over complexity - Simple, understandable plans
  2. Action-oriented - Every section leads to concrete actions
  3. Flexibility - Plans adapt to changing circumstances
  4. Accountability - Clear ownership and deadlines
  5. Measurable - Success criteria are objective
  1. 清晰优先于复杂 - 简单易懂的计划
  2. 行动导向 - 每个章节都指向具体行动
  3. 灵活性 - 计划可适应环境变化
  4. 问责制 - 明确责任人和截止日期
  5. 可衡量 - 成功标准客观可量化

Planning Methodology

规划方法论

Step 1: Vision & Objectives (< 5 minutes)

步骤1：愿景与目标（<5分钟）

Purpose: Define what you want to achieve and why
Questions to answer:
  • What is the desired end state?
  • Why is this project important?
  • Who benefits from this project?
  • What problem does this solve?
Output format:
markdown
undefined
目的：定义要实现的目标及原因
需回答的问题：
  • 期望的最终状态是什么？
  • 这个项目为什么重要？
  • 谁会从项目中受益？
  • 项目解决了什么问题？
输出格式：
markdown
undefined

Vision & Objectives

愿景与目标

Vision Statement

愿景声明

[One paragraph describing the ideal outcome]
[描述理想结果的段落]

Primary Objective

主要目标

[Main goal - SMART format: Specific, Measurable, Achievable, Relevant, Time-bound]
[核心目标 - 遵循SMART格式：具体、可衡量、可实现、相关性、时限性]

Secondary Objectives

次要目标

  • Objective 1: [SMART format]
  • Objective 2: [SMART format]
  • 目标1：[SMART格式]
  • 目标2：[SMART格式]

Alignment

对齐性

  • Strategic Fit: [How this aligns with broader goals]
  • Stakeholders: [Who cares about this and why]
  • Value Proposition: [Why now, why this approach]
undefined
  • 战略契合度：[与更广泛目标的对齐方式]
  • 利益相关者：[关注项目的人员及原因]
  • 价值主张：[为什么选择现在实施，为什么采用此方案]
undefined

Step 2: Scope & Deliverables (< 5 minutes)

步骤2：范围与交付成果（<5分钟）

Purpose: Define boundaries and specific outputs
Questions to answer:
  • What's included in this project?
  • What's explicitly excluded?
  • What tangible deliverables will we produce?
  • What are the acceptance criteria?
Output format:
markdown
undefined
目的：定义项目边界与具体产出
需回答的问题：
  • 项目包含哪些内容？
  • 项目明确排除哪些内容？
  • 会产出哪些有形交付成果？
  • 验收标准是什么？
输出格式：
markdown
undefined

Scope & Deliverables

范围与交付成果

In Scope

包含范围

  • [Specific activity/outcome 1]
  • [Specific activity/outcome 2]
  • [具体活动/产出1]
  • [具体活动/产出2]

Out of Scope

排除范围

  • [What we're NOT doing 1]
  • [What we're NOT doing 2]
  • [明确不做的内容1]
  • [明确不做的内容2]

Deliverables

交付成果

  1. Deliverable 1: [Description]
    • Acceptance Criteria: [How we know it's done]
    • Format: [Document, event, product, etc.]
  2. Deliverable 2: [Description]
    • Acceptance Criteria: [How we know it's done]
    • Format: [Format]
  1. 交付成果1：[描述]
    • 验收标准：[如何判断完成]
    • 格式：[文档、活动、产品等]
  2. 交付成果2：[描述]
    • 验收标准：[如何判断完成]
    • 格式：[格式类型]

Constraints

约束条件

  • Budget: [Budget limitation]
  • Time: [Time constraint]
  • Resources: [Resource constraints]
  • Quality: [Non-negotiable quality standards]
undefined
  • 预算：[预算限制]
  • 时间：[时间约束]
  • 资源：[资源限制]
  • 质量：[不可妥协的质量标准]
undefined

Step 3: Action Steps (< 10 minutes)

步骤3：行动步骤（<10分钟）

Purpose: Break down work into executable tasks
Sequencing principles:
  1. Dependencies first - Complete prerequisites before dependent tasks
  2. Quick wins early - Build momentum with achievable tasks
  3. Parallel work - Identify tasks that can happen simultaneously
  4. Critical path - Highlight tasks that determine overall timeline
Output format:
markdown
undefined
目的：将工作分解为可执行的任务
排序原则：
  1. 先处理依赖任务 - 完成前置任务再执行依赖任务
  2. 早期快速获胜 - 通过可实现的任务建立动力
  3. 并行工作 - 识别可同时进行的任务
  4. 关键路径 - 突出决定整体时间线的任务
输出格式：
markdown
undefined

Action Steps

行动步骤

Phase 1: [Phase Name] (Weeks 1-2)

阶段1：[阶段名称]（第1-2周）

Step 1.1: [Action Verb] [What]

步骤1.1：[动作动词] [任务内容]

  • Description: [What needs to be done]
  • Owner: [Who is responsible]
  • Duration: [Estimated time]
  • Dependencies: [What must be done first]
  • Output: [What this produces]
  • Verification: [How to confirm completion]
  • 描述：[需要完成的工作]
  • 负责人：[责任人]
  • 时长：[预估时间]
  • 依赖项：[必须先完成的任务]
  • 产出：[任务成果]
  • 验证方式：[如何确认完成]

Step 1.2: [Action Verb] [What]

步骤1.2：[动作动词] [任务内容]

[Same structure]
[相同结构]

Phase 2: [Phase Name] (Weeks 3-4)

阶段2：[阶段名称]（第3-4周）

[Continue with steps]
[继续添加步骤]

Critical Path

关键路径

Tasks that determine overall timeline:
  1. Step X.X → Step Y.Y → Step Z.Z
undefined
决定整体时间线的任务：
  1. 步骤X.X → 步骤Y.Y → 步骤Z.Z
undefined

Step 4: Resources Required (< 5 minutes)

步骤4：所需资源（<5分钟）

Purpose: Identify what's needed to execute
Categories:
  • People: Skills, roles, time commitment
  • Budget: Money for materials, services, licenses
  • Materials: Physical items, equipment, supplies
  • Time: Duration, deadlines, availability
  • Knowledge: Training, expertise, information
  • Tools: Software, platforms, systems
Output format:
markdown
undefined
目的：识别执行项目所需的资源
分类：
  • 人员：技能、角色、时间投入
  • 预算：物料、服务、许可证费用
  • 物料：实物、设备、用品
  • 时间：时长、截止日期、可用时间
  • 知识：培训、专业技能、信息
  • 工具：软件、平台、系统
输出格式：
markdown
undefined

Resources Required

所需资源

People

人员

  • Role 1: [Skills needed], [Time commitment], [Availability]
  • Role 2: [Skills], [Time], [Availability]
  • 角色1：[所需技能]、[时间投入]、[可用时间]
  • 角色2：[所需技能]、[时间投入]、[可用时间]

Budget

预算

CategoryItemEstimated CostStatus
Materials[Item]$X,XXXApproved/Pending
Services[Service]$X,XXXApproved/Pending
Total Budget: $X,XXX
分类项目预估成本状态
物料[项目]$X,XXX已批准/待批准
服务[服务]$X,XXX已批准/待批准
总预算：$X,XXX

Materials & Equipment

物料与设备

  • [Item 1]: [Quantity], [Specifications], [Source]
  • [Item 2]: [Quantity], [Specifications], [Source]
  • [物料1]：[数量]、[规格]、[来源]
  • [物料2]：[数量]、[规格]、[来源]

Knowledge & Training

知识与培训

  • [Skill/Knowledge 1]: [Who needs it], [How to acquire]
  • [Skill/Knowledge 2]: [Who needs it], [How to acquire]
  • [技能/知识1]：[需求人员]、[获取方式]
  • [技能/知识2]：[需求人员]、[获取方式]

Tools & Systems

工具与系统

  • [Tool 1]: [Purpose], [License/Access], [Cost]
  • [Tool 2]: [Purpose], [License/Access], [Cost]
undefined
  • [工具1]：[用途]、[许可证/访问权限]、[成本]
  • [工具2]：[用途]、[许可证/访问权限]、[成本]
undefined

Step 5: Timeline & Milestones (< 5 minutes)

步骤5：时间线与里程碑（<5分钟）

Purpose: Set deadlines and create accountability
Milestone criteria:
  • Significant progress point
  • Measurable completion
  • Enables next phase
  • Stakeholder visibility
Output format:
markdown
undefined
目的：设置截止日期并建立问责机制
里程碑标准：
  • 重要的进度节点
  • 可衡量的完成状态
  • 支持下一阶段推进
  • 利益相关者可见
输出格式：
markdown
undefined

Timeline & Milestones

时间线与里程碑

Overall Timeline

整体时间线

Start Date: YYYY-MM-DD End Date: YYYY-MM-DD Total Duration: [X weeks/months]
开始日期：YYYY-MM-DD 结束日期：YYYY-MM-DD 总时长：[X周/月]

Milestones

里程碑

Milestone 1: [Name] - [Date]

里程碑1：[名称] - [日期]

  • Criteria: [What must be complete]
  • Deliverables: [What to show]
  • Checkpoint: [Review meeting/decision point]
  • 标准：[必须完成的内容]
  • 交付成果：[需展示的成果]
  • 检查点：[评审会议/决策点]

Milestone 2: [Name] - [Date]

里程碑2：[名称] - [日期]

[Same structure]
[相同结构]

Gantt Chart (Text-based)

文本化Gantt Chart

Week 1  : [█████████░░░] Phase 1 (Step 1.1-1.3)
Week 2  : [░░░░█████████] Phase 1 (Step 1.4-1.6)
Week 3  : [█████████░░░] Phase 2 (Step 2.1-2.3)
Week 4  : [░░░░█████████] Phase 2 Complete
Week 1  : [█████████░░░] 阶段1（步骤1.1-1.3）
Week 2  : [░░░░█████████] 阶段1（步骤1.4-1.6）
Week 3  : [█████████░░░] 阶段2（步骤2.1-2.3）
Week 4  : [░░░░█████████] 阶段2完成

Key Dates

关键日期

undefined
  • [YYYY-MM-DD]：[事件/截止日期]
  • [YYYY-MM-DD]：[事件/截止日期]
undefined

Step 6: Risks & Contingencies (< 5 minutes)

步骤6：风险与应急预案（<5分钟）

Purpose: Anticipate problems and plan responses
Risk categories:
  • External: Market changes, regulations, competition
  • Resource: Budget cuts, people unavailable, materials
  • Technical: Complexity, dependencies, unknowns
  • Stakeholder: Resistance, competing priorities, misalignment
  • Timeline: Delays, scope creep, optimism bias
Output format:
markdown
undefined
目的：预判问题并制定应对方案
风险分类：
  • 外部：市场变化、法规、竞争
  • 资源：预算削减、人员不可用、物料短缺
  • 技术：复杂度、依赖项、未知因素
  • 利益相关者：阻力、竞争优先级、对齐问题
  • 时间线：延迟、范围蔓延、乐观偏差
输出格式：
markdown
undefined

Risks & Contingencies

风险与应急预案

Risk 1: [Description]

风险1：[描述]

Category: [External/Resource/Technical/Stakeholder/Timeline] Probability: [High/Medium/Low] Impact: [High/Medium/Low] Risk Score: [Probability × Impact = Score]
Mitigation: [How to prevent] Contingency: [What to do if it happens] Early Warning Signs: [Indicators this is occurring] Owner: [Who monitors this]
分类：[外部/资源/技术/利益相关者/时间线] 概率：[高/中/低] 影响：[高/中/低] 风险评分：[概率 × 影响 = 评分]
缓解措施：[预防方法] 应急预案：[发生后的应对方案] 早期预警信号：[风险发生的迹象] 负责人：[监控风险的人员]

Risk 2: [Description]

风险2：[描述]

[Same structure]
[相同结构]

Risk Matrix

风险矩阵

Impact
High   │ R3 │ R1 │ R1 │
Medium │ R5 │ R2 │ R1 │
Low    │ R7 │ R5 │ R2 │
       └────┴────┴────┘
         L   M   H
       Probability
undefined
Impact
High   │ R3 │ R1 │ R1 │
Medium │ R5 │ R2 │ R1 │
Low    │ R7 │ R5 │ R2 │
       └────┴────┴────┘
         L   M   H
       Probability
undefined

Step 7: Success Metrics (< 3 minutes)

步骤7：成功指标（<3分钟）

Purpose: Define measurable outcomes
SMART criteria:
  • Specific: Exact metric
  • Measurable: Quantifiable
  • Achievable: Realistic
  • Relevant: Aligned with objectives
  • Time-bound: By when
Output format:
markdown
undefined
目的：定义可衡量的成果
SMART标准：
  • 具体：精确的指标
  • 可衡量：可量化
  • 可实现：现实可行
  • 相关性：与目标对齐
  • 时限性：明确截止时间
输出格式：
markdown
undefined

Success Metrics

成功指标

Primary Metrics

主要指标

  • Metric 1: [Name]
    • Target: [Specific number/outcome]
    • Measurement: [How to measure]
    • Frequency: [How often to check]
    • Baseline: [Current state]
  • Metric 2: [Name] [Same structure]
  • 指标1：[名称]
    • 目标：[具体数值/成果]
    • 测量方式：[如何测量]
    • 频率：[检查频率]
    • 基线：[当前状态]
  • 指标2：[名称] [相同结构]

Secondary Metrics

次要指标

  • [指标3]：[目标]
  • [指标4]：[目标]

Completion Criteria

完成标准

  • All deliverables accepted by stakeholders
  • Primary metrics meet/exceed targets
  • Budget within ±10% of estimate
  • Timeline within ±10% of estimate
  • Stakeholder satisfaction ≥ 8/10
  • No critical issues remaining
  • 所有交付成果获得利益相关者认可
  • 主要指标达到/超过目标
  • 预算控制在预估的±10%以内
  • 时间线控制在预估的±10%以内
  • 利益相关者满意度≥8/10
  • 无未解决的关键问题

Post-Project Review

项目后评审

  • Review Date: [2-4 weeks after completion]
  • Participants: [Who attends]
  • Topics: Lessons learned, metrics achieved, improvements
undefined
  • 评审日期：[完成后2-4周]
  • 参与人员：[参会人员]
  • 议题：经验总结、指标达成情况、改进方向
undefined

Complete Plan Template

完整计划模板

markdown
---
plan_id: PLAN-YYYYMMDD-HHMM-{slug}
title: [Project Name]
created: YYYY-MM-DD HH:MM
status: draft
category: [business|personal|creative|academic|event|organizational]
phase: planning
priority: [critical|high|medium|low]
---
markdown
---
plan_id: PLAN-YYYYMMDD-HHMM-{slug}
title: [项目名称]
created: YYYY-MM-DD HH:MM
status: draft
category: [business|personal|creative|academic|event|organizational]
phase: planning
priority: [critical|high|medium|low]
---

🎯 Project Plan: [Project Name]

🎯 项目计划：[项目名称]

Vision & Objectives

愿景与目标

[Vision statement and SMART objectives]
[愿景声明和SMART目标]

Scope & Deliverables

范围与交付成果

[What's included, excluded, and delivered]
[包含内容、排除内容及交付成果]

Action Steps

行动步骤

[Phased, sequenced tasks with owners]
[分阶段、有序的任务及责任人]

Resources Required

所需资源

[People, budget, materials, time, knowledge, tools]
[人员、预算、物料、时间、知识、工具]

Timeline & Milestones

时间线与里程碑

[Dates, milestones, Gantt chart]
[日期、里程碑、Gantt chart]

Risks & Contingencies

风险与应急预案

[Identified risks with mitigation strategies]
[已识别风险及缓解策略]

Success Metrics

成功指标

[Measurable outcomes and completion criteria]
[可衡量的成果及完成标准]

Notes & Considerations

备注与注意事项

[Additional context, assumptions, dependencies]
undefined
[额外背景、假设、依赖项]
undefined

Quality Standards

质量标准

Completeness

完整性

  • All 7 sections present and filled
  • Each action step has owner and deadline
  • Resources are realistic and available
  • Risks have mitigation plans
  • Success metrics are SMART
  • 所有7个章节均已填写
  • 每个行动步骤都有责任人和截止日期
  • 资源配置现实且可用
  • 风险均有应对方案
  • 成功指标符合SMART标准

Clarity

清晰度

  • Anyone can understand the plan
  • No jargon without explanation
  • Concrete examples provided
  • Ambiguity eliminated
  • 任何人都能理解计划内容
  • 无未解释的行话
  • 提供具体示例
  • 消除歧义

Actionability

可执行性

  • Next steps are clear
  • Owners know what to do
  • Timeline is realistic
  • Resources are secured
  • 下一步行动明确
  • 责任人清楚自身任务
  • 时间线现实可行
  • 资源已落实

Common Project Types

常见项目类型

Business Project Example Triggers

商业项目触发示例

  • Product launch, marketing campaign, sales initiative
  • Process improvement, efficiency project
  • Market expansion, partnership development
  • 产品发布、营销活动、销售举措
  • 流程优化、效率提升项目
  • 市场拓展、合作伙伴开发

Personal Project Example Triggers

个人项目触发示例

  • Career transition, skill development
  • Health/fitness goal, lifestyle change
  • Financial goal, savings plan
  • 职业转型、技能提升
  • 健康/健身目标、生活方式改变
  • 财务目标、储蓄计划

Creative Project Example Triggers

创意项目触发示例

  • Book/article writing, content creation
  • Art project, exhibition planning
  • Music production, album release
  • 书籍/文章写作、内容创作
  • 艺术项目、展览策划
  • 音乐制作、专辑发行

Academic Project Example Triggers

学术项目触发示例

  • Research project, thesis planning
  • Study program, exam preparation
  • Conference presentation, paper publication
  • 研究项目、论文规划
  • 学习方案、考试准备
  • 会议演讲、论文发表

Event Planning Example Triggers

活动策划触发示例

  • Conference/workshop organization
  • Wedding/celebration planning
  • Community event, fundraiser
  • 会议/研讨会组织
  • 婚礼/庆典策划
  • 社区活动、筹款活动

Organizational Change Example Triggers

组织变革触发示例

  • Team restructuring, role changes
  • Culture initiative, value implementation
  • Policy change, process adoption
  • 团队重组、角色调整
  • 文化建设、价值观落地
  • 政策变更、流程 adoption

Continue Planning Workflow

计划续编工作流

When user says "continue plan":
  1. Load active plan from 
    docs/plan.md
  2. Check phase:
    • Planning: Add details, refine sections
    • Execution: Update progress, mark steps complete
    • Monitoring: Review metrics, adjust timeline
  3. Update status as work progresses
当用户说“继续计划”时：
  1. 从
    docs/plan.md
    加载活跃计划
  2. 检查阶段：
    • 规划阶段：补充细节、完善章节
    • 执行阶段：更新进度、标记已完成步骤
    • 监控阶段：评审指标、调整时间线
  3. 随着工作推进更新状态

Format Validation

格式验证

Before finalizing:
  • Frontmatter complete (plan_id, title, status, category, phase, priority)
  • All 7 sections present
  • Vision is inspiring and clear
  • Objectives are SMART
  • Action steps have owners and deadlines
  • Resources identified and available
  • Timeline is realistic
  • Risks have contingencies
  • Success metrics are measurable
  • Master tracker updated
最终确定前需检查：
  • 前置元数据完整（plan_id、title、status、category、phase、priority）
  • 所有7个章节均存在
  • 愿景清晰且有激励性
  • 目标符合SMART标准
  • 行动步骤有责任人和截止日期
  • 资源已识别且可用
  • 时间线现实可行
  • 风险有应急预案
  • 成功指标可衡量
  • 主跟踪器已更新

Example Usage

示例用法

Scenario: Product Launch Plan
User: "Create a plan for launching our new mobile app"
Claude:
  1. Checks 
    docs/plan.md
    - no active plan
  2. Asks clarifying questions:
    • Who is the target audience?
    • What's the launch date goal?
    • What's the budget?
  3. Creates 
    PLAN-20251118-1430-mobile-app-launch.md
    :
    • Vision: Achieve 10K downloads in first month
    • Objectives: SMART goals for downloads, revenue, engagement
    • Scope: Features in v1.0, marketing channels, launch events
    • Action Steps: Development, testing, marketing, launch
    • Resources: Team roles, budget, tools
    • Timeline: 12-week timeline with milestones
    • Risks: Technical delays, market reception, competition
    • Metrics: Downloads, DAU, revenue, ratings
  4. Updates 
    docs/plan.md
    with active plan
Scenario: Personal Learning Goal
User: "Help me plan learning Python for data science"
Claude:
  1. Checks for active plan
  2. Creates structured learning plan:
    • Vision: Become job-ready data scientist in 6 months
    • Objectives: Complete courses, build portfolio projects
    • Scope: Topics to cover, projects to build
    • Action Steps: Weekly study schedule, hands-on practice
    • Resources: Courses, books, datasets, tools
    • Timeline: Month-by-month progression
    • Risks: Time management, motivation, difficulty
    • Metrics: Courses completed, projects finished, job applications
场景：产品发布计划
用户：“为我们的新移动应用创建发布计划”
Claude：
  1. 检查
    docs/plan.md
    - 无活跃计划
  2. 询问澄清问题：
    • 目标受众是谁？
    • 发布日期目标是什么？
    • 预算是多少？
  3. 创建
    PLAN-20251118-1430-mobile-app-launch.md
    ：
    • 愿景：首月实现1万次下载
    • 目标：下载量、收入、用户参与度的SMART目标
    • 范围：v1.0功能、营销渠道、发布活动
    • 行动步骤：开发、测试、营销、发布
    • 资源：团队角色、预算、工具
    • 时间线：12周时间线及里程碑
    • 风险：技术延迟、市场反馈、竞争
    • 指标：下载量、日活跃用户（DAU）、收入、评分
  4. 更新
    docs/plan.md
    中的活跃计划
场景：个人学习目标
用户：“帮我规划学习Python用于数据科学”
Claude：
  1. 检查是否存在活跃计划
  2. 创建结构化学习计划：
    • 愿景：6个月内成为可求职的数据科学家
    • 目标：完成课程、构建作品集项目
    • 范围：需学习的主题、需构建的项目
    • 行动步骤：每周学习计划、实操练习
    • 资源：课程、书籍、数据集、工具
    • 时间线：逐月推进计划
    • 风险：时间管理、动力、学习难度
    • 指标：完成课程数量、完成项目数量、求职申请数量

Integration with Implementation Planner

与Implementation Planner的集成

When planning involves software development:
  1. Use this skill for overall project planning:
    • Business objectives
    • Stakeholder management
    • Resource allocation
    • Timeline
  2. Use 
    implementation-planner
    for technical implementation:
    • Code architecture
    • File changes
    • Testing strategy
    • Deployment
  3. Cross-reference plans:
    • Implementation plan referenced in technical deliverables
    • Project plan tracks implementation as one action step
This skill creates actionable, complete plans for any project type while maintaining consistent format and tracking.
当规划涉及软件开发时：
  1. 使用本技能进行整体项目规划：
    • 商业目标
    • 利益相关者管理
    • 资源分配
    • 时间线
  2. 使用
    implementation-planner
    进行技术实施规划：
    • 代码架构
    • 文件变更
    • 测试策略
    • 部署
  3. 交叉引用计划：
    • 技术交付成果中引用实施计划
    • 项目计划将实施作为一个行动步骤进行跟踪
本技能可为任何类型的项目创建可执行的完整计划，同时保持格式一致性和可跟踪性。