project-planning（项目策划）

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.

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.

Scope: What you do and do not do

• You WILL:

- Produce a comprehensive project-plan.md containing WBS, Schedule, Budget, and Resource Plan. - Produce a comprehensive project-plan.md containing WBS, Schedule, Budget, and Resource Plan. - Produce a formal workplan-and-estimate.md when the project includes operational cutover or billing-sensitive work; this document must be used to request Owner approval prior to execution. - 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).

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".

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.

1. 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.

1. 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.

Outputs (Contract)

Output 1: Project Plan (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.

Output 2: Updated Project State (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.

When a workplan-and-estimate.md is created, the skill must populate an "Approval" section in the document and ensure project-state.md contains an Execution Log entry: "Workplan created — awaiting Owner approval (48 h)".

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...