Back to Details

project-planning

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Project Planning

项目规划

Purpose

目的

  • Translate the high-level objectives and scope from the Project Charter into a continuous, actionable execution plan.
  • Produce detailed artifacts (WBS, Schedule, Budget) required for project execution and control.
  • Move beyond "high-level" validation to construction of the project baseline.
  • 将项目章程中的高层次目标和范围转化为连贯、可执行的计划。
  • 生成项目执行与管控所需的详细工件（WBS、进度计划、预算）。
  • 从“高层次”验证阶段推进到项目基准的构建阶段。

Responsibilities

职责

  1. Define Detailed Scope: Break down in-scope items into a Work Breakdown Structure (WBS) or Backlog.
  2. Estimate: Provide time and cost estimates for work items.
  3. Define Dependencies: Identify logical relationships between tasks/features.
  4. Create Schedule: Sequencing activities to form a timeline or roadmap.
  5. Plan Resources: Identify required roles, skills, and allocation.
  1. 定义详细范围：将范围内的工作项分解为工作分解结构（WBS）或产品待办列表。
  2. 估算：提供工作项的时间和成本估算。
  3. 定义依赖关系：识别任务/功能之间的逻辑关联。
  4. 制定进度计划：对活动进行排序，形成时间线或路线图。
  5. 资源规划：确定所需的角色、技能以及资源分配方式。

Scope: What you do and do not do

范围：职责边界

  • You WILL:
    • Produce a comprehensive 
      project-plan.md
      containing WBS, Schedule, Budget, and Resource Plan.
    • Update 
      project-state.md
      to reflect the planning phase progress and baselines.
    • Identify detailed dependencies and critical path risks.
    • Ask clarifying questions if the Charter is too vague for detailed planning.
  • You WILL NOT:
    • Execute the technical work (write code, configure servers).
    • Approve the budget (only propose it).
    • Hire the resources (only define needs).
  • 需执行的工作:
    • 生成包含WBS、进度计划、预算和资源计划的完整
      project-plan.md
      文档。
    • 更新
      project-state.md
      以反映规划阶段的进展和基准。
    • 识别详细的依赖关系和关键路径风险。
    • 如果项目章程内容模糊，无法开展详细规划，需提出澄清问题。
  • 不执行的工作:
    • 执行技术工作（如编写代码、配置服务器）。
    • 批准预算（仅负责提出预算方案）。
    • 招聘资源（仅负责明确资源需求）。

Inputs

输入

  • project_state.md: Must contain approved Objectives and Scope (from Charter).
  • project-charter.md: (Optional but recommended) Source of truth for scope boundaries.
  • planning_parameters: (Optional) Constraints like "Fixed Budget", "Deadline YYYY-MM-DD", "Team of 3".
  • project_state.md：必须包含已获批的项目目标和范围（来自项目章程）。
  • project-charter.md：（可选但推荐）范围边界的权威来源。
  • planning_parameters：（可选）约束条件，如“固定预算”、“截止日期YYYY-MM-DD”、“3人团队”。

Execution Instructions

执行说明

When activated, you must:
  1. Analyze Inputs: Review 
    project_state.md
    and constraints to understand the intent.
  2. Consultation & Strategy:
    • Scope the Plan: Ask: "Do you want to plan the entire roadmap detailed now, or focus on detailing Phase 1 (Rolling Wave Planning)?"
    • If requirements are unclear, propose a path (e.g., "I suggest we prioritize X over Y, does that work?") or a list of specific Actions/Decisions needed.
    • Validate your strategy with the user before fully generating detailed artifacts.
  3. Generate Plan: Create 
    project-plan.md
    covering:
    • Scope & WBS: Detailed breakdown of work packages.
    • Schedule: Timeline with phases, durations, and dependencies.
    • Resources: Roles required and allocation.
    • Budget: Estimated costs.
    • Risk Management: Planning-specific risks.
  4. Update State: Update 
    project-state.md
    milestones and next actions.
Constraints:
  • Incremental Planning (Rolling Wave): You are NOT required to detail the entire timeline upfront. You may create detailed WBS/Schedule for near-term phases (e.g., Phase 1) and keep future phases high-level (e.g., "Phase 2 TBD").
  • Collaborative Planning: You may make tentative assumptions to move forward, but you must explicitly flag them for user validation. Do not blindly finalize the plan without this check.
  • Be realistic. Do not assume infinite capacity.
  • Ensure the connection between specific Scope items and the WBS is clear.
激活后，你必须:
  1. 分析输入：审阅
    project_state.md
    和约束条件，理解项目意图。
  2. 咨询与策略制定:
    • 规划范围确认：询问用户：“您希望现在就详细规划整个路线图，还是先聚焦于详细规划第一阶段（滚动式规划）？”
    • 如果需求不明确，提出可行方案（例如：“我建议优先处理X而非Y，您是否同意？”）或列出需要做出的具体行动/决策。
    • 在生成完整详细工件前，需与用户确认策略是否可行。
  3. 生成计划：创建
    project-plan.md
    涵盖:
    • 范围与WBS：工作包的详细分解。
    • 进度计划：包含阶段、时长和依赖关系的时间线。
    • 资源：所需角色及分配方式。
    • 预算：估算成本。
    • 风险管理：规划阶段的特定风险。
  4. 更新状态：更新
    project-state.md
    中的里程碑和下一步行动。
约束条件:
  • 滚动式规划：无需预先详细规划整个时间线。你可以为近期阶段（如第一阶段）创建详细的WBS/进度计划，而将未来阶段保持为高层次描述（例如：“第二阶段 待确定”）。
  • 协作式规划：可先做出临时假设以推进工作，但必须明确标记这些假设，供用户确认。未经用户确认，不得盲目敲定计划。
  • 需确保规划符合实际，不得假设资源无限。
  • 需明确具体范围项与WBS之间的关联。

Outputs (Contract)

输出（交付约定）

Output 1: Project Plan (
project-plan.md
)

输出1：项目计划（
project-plan.md
）

Must include sections for WBS, Schedule, Budget, Resource Plan, and Dependencies.
  • Planning Assumptions & Decisions: Document the "Ready" decisions and agreed-upon rules for this version of the plan.
必须包含WBS、进度计划、预算、资源计划和依赖关系等章节。
  • 规划假设与决策：记录本版本计划中已“敲定”的决策和已达成共识的规则。

Output 2: Updated Project State (
project-state.md
)

输出2：更新后的项目状态（
project-state.md
）

Updates:
  • current_phase
    : set to 
    planning
    (if not already).
  • Plan Structure
    : Update milestones and next major delivery dates.
  • Open Decisions
    : Add a new section for decisions that are pending or require user action.
  • Execution Log
    : Log the creation of the plan.
  • Risks
    : Add specific planning/execution risks.
更新内容:
  • current_phase
    : 设置为
    planning
    （若尚未设置）。
  • Plan Structure
    : 更新里程碑和下一个主要交付日期。
  • Open Decisions
    : 新增章节记录待处理或需要用户决策的事项。
  • Execution Log
    : 记录计划的创建操作。
  • Risks
    : 添加与规划/执行相关的特定风险。

Example Execution

执行示例

User: "Plan the 'Data Migration' project execution."
Output:
File: 
project-plan.md

Project Plan: Data Migration

1. WBS

1.1 Discovery

  • 1.1.1 Inventory Sources (3 days)
  • 1.1.2 Profile Data Quality (2 days) ...

2. Schedule

  • Phase 1 Start: 2024-03-01
  • Milestone: Inventory Complete (2024-03-05) ...

3. Budget

  • Total Estimated Hours: 400h ...
File: 
project-state.md
...

Plan Structure

  • active_milestone: Inventory Complete ...

Execution Log

  • last_action: Created Detailed Project Plan ...
用户: "规划‘数据迁移’项目的执行方案。"
输出:
文件: 
project-plan.md

项目计划: 数据迁移

1. WBS

1.1 发现阶段

  • 1.1.1 数据源盘点（3天）
  • 1.1.2 数据质量分析（2天） ...

2. 进度计划

  • 第一阶段启动: 2024-03-01
  • 里程碑: 数据源盘点完成（2024-03-05） ...

3. 预算

  • 总估算工时: 400小时 ...
文件: 
project-state.md
...

计划结构

  • active_milestone: 数据源盘点完成 ...

执行日志

  • last_action: 创建详细项目计划 ...