Core Positioning
This is a skill focused onproject execution planning, helping you go from idea to implementation, systematically plan the project path, and ensure the project is delivered on time and with high quality. Unlike product requirements analysis (PRD), this skill focuses more onhow to do itandhow to do it well。
Applicable Scenarios
Project Initiation Stage
- "I want to build an e-commerce mini program, help me plan it"
- "My boss asked me to lead a new project, where do I start?"
- "How long will this requirement roughly take to complete?"
Project Planning Stage
- "Help me break down the tasks for this project"
- "These features have dependencies, how should I arrange the order?"
- "How can I complete this project within 3 months?"
Project Execution Stage
- "The project is delayed, how should I adjust the plan?"
- "Help me check whether this task breakdown is reasonable"
- "How can I track the team's project progress?"
Project Closing Stage
- "The project is about to be delivered, what items are on the checklist?"
- "How do I conduct a project retrospective?"
- "How do I consolidate project experience?"
How to Use
Quick Start
Directly describe your project situation:
"帮我规划一个项目：开发一个团队协作工具，团队3个人，2个月后要上线"
"这是我们产品的功能清单，帮我做个项目计划"
"项目需求发生了变更，帮我重新规划一下路径"
Provide Detailed Information
The more information you provide, the more accurate the plan:
Basic Information：
- Project name and goals
- Team size and role division
- Time constraints and key milestones
- Budget and resource constraints
Project Background(optional):
- Whether there are existing systems that need integration
- Technology stack requirements or constraints
- Relevant historical project experience
Reference Documents(optional):
- Upload requirements documents, design drafts, technical solutions, etc.
- Provide reference cases of similar projects
Project Planning Framework
I will help you complete the following planning work:
1. Project Understanding and Breakdown
Project Background Analysis：
- Understand the project's core goals and value
- Identify key stakeholders
- Clarify project boundaries and constraints
Task Breakdown (WBS)：
- Break the project down into manageable modules
- Identify dependencies between modules
- Estimate the workload of each task
Priority Ranking：
- Rank by business value
- Rank by dependencies
- Rank by risk level
2. Milestones and Time Planning
Milestone Setting：
- Define clear phased goals
- Set verifiable deliverables
- Reserve buffer time
Timeline Planning：
- Draw the project timeline
- Plan the critical path
- Balance resource allocation
Progress Scheduling：
- Arrange parallel tasks reasonably
- Avoid over-concentration of resources
- Reserve contingency time
3. Team and Resource Planning
Roles and Responsibilities：
- Clarify team member roles
- Define responsibility boundaries
- Establish reporting relationships
Resource Allocation：
- Assess human resource needs
- Plan technical/tool resources
- Budget and time resources
Collaboration Mechanisms：
- Determine communication frequency and methods
- Establish synchronization mechanisms
- Plan collaboration tools
4. Risk Management
Risk Identification：
- Technical risks (technical difficulties, third-party dependencies)
- Resource risks (personnel changes, insufficient resources)
- Time risks (requirement changes, schedule delays)
- Quality risks (technical debt, test coverage)
Risk Assessment：
- Assess the probability of risk occurrence
- Assess the degree of risk impact
- Determine risk priorities
Response Strategies：
- Develop preventive measures
- Prepare contingency plans
- Assign risk owners
5. Quality Assurance Planning
Quality Standards：
- Define quality goals and metrics
- Establish acceptance criteria
- Determine quality checkpoints
Testing Strategy：
- Plan test types and scope
- Schedule testing time
- Define testing standards
Review Mechanisms：
- Plan review checkpoints
- Define review standards
- Establish a feedback loop
Outputs
After completing the planning, you will obtain the following outputs:
Project Overview
- Project background and goals
- Project scope and boundaries
- Key constraints
Task Breakdown
- Work Breakdown Structure (WBS)
- Task dependency diagram
- Task priority ranking
Time Planning
- Project milestones
- Detailed schedule
- Critical path identification
Team Collaboration
- Role assignment
- Communication plan
- Collaboration tool recommendations
Risk Register
- List of identified risks
- Risk assessment matrix
- Response strategies and contingency plans
Quality Assurance
- Quality standards
- Acceptance criteria
- Checklist
Project Planning Templates
Quick Planning Template
# [项目名称] 规划方案
## 项目概述
- **项目目标**: [一句话描述项目要实现什么]
- **交付物**: [项目最终交付什么]
- **时间约束**: [截止日期或时间范围]
- **团队规模**: [多少人参与]
## 核心任务
### 阶段一：[名称]
- [ ] 任务1
- [ ] 任务2
- [ ] 任务3
### 阶段二：[名称]
- [ ] 任务4
- [ ] 任务5
- [ ] 任务6
## 里程碑
| 时间点 | 里程碑 | 交付物 |
|--------|--------|--------|
| Date1 | M1 | Deliverable1 |
| Date2 | M2 | Deliverable2 |
## 风险识别
| 风险 | 影响 | 概率 | 应对措施 |
|------|------|------|----------|
| Risk1 | High | Medium | Mitigation |
## 下一步行动
1. [ ] Action1
2. [ ] Action2
3. [ ] Action3
Detailed Planning Template
# 项目规划文档
## 1. 项目定义
### 1.1 项目背景
[项目产生的背景和原因]
### 1.2 项目目标
- **主要目标**: [核心目标]
- **次要目标**: [辅助目标]
- **成功标准**: [如何判断项目成功]
### 1.3 项目范围
- **包含范围**: [做的是什么]
- **排除范围**: [不做什么]
- **边界条件**: [什么情况下算完成]
## 2. 任务分解
### 2.1 工作分解结构(WBS)
Project ├── Module 1 │ ├── Task 1.1 │ ├── Task 1.2 │ └── Task 1.3 ├── Module 2 │ ├── Task 2.1 │ └── Task 2.2 └── Module 3 ├── Task 3.1 └── Task 3.2
### 2.2 任务详情
| ID | 任务名称 | 负责人 | 工期 | 依赖 | 优先级 |
|----|----------|--------|------|------|--------|
| T1 | 任务1 | PersonA | 3天 | - | P0 |
| T2 | 任务2 | PersonB | 2天 | T1 | P0 |
## 3. 时间规划
### 3.1 里程碑
| 日期 | 里程碑 | 验收标准 | 状态 |
|------|--------|----------|------|
| Date | M1 | Criteria | Done |
### 3.2 详细进度
[甘特图或时间轴]
### 3.3 关键路径
[标识关键路径任务]
## 4. 资源规划
### 4.1 团队组成
| 角色 | 姓名 | 职责 | 工作量 |
|------|------|------|--------|
| 负责人 | XXX | 整体把控 | 50% |
| 开发 | XXX | 技术实现 | 100% |
### 4.2 资源需求
- 硬件资源
- 软件资源
- 外部服务
## 5. 风险管理
### 5.1 风险清单
| ID | 风险描述 | 影响 | 概率 | 风险等级 | 应对策略 | 责任人 |
|----|----------|------|------|----------|----------|--------|
| R1 | XXX | 高 | 中 | 高 | XXX | XXX |
### 5.2 应急预案
[关键风险的应急预案]
## 6. 沟通计划
### 6.1 常规会议
| 会议 | 频率 | 参与者 | 输出 |
|------|------|--------|------|
| 站会 | 每天 | 团队 | 进展同步 |
| 周会 | 每周 | 团队+干系人 | 进度汇报 |
### 6.2 报告机制
- 日报/周报模板
- 进度报告频率
- 升级流程
## 7. 质量保障
### 7.1 质量目标
- 功能完整性: 100%
- Bug数量: < 10
- 性能指标: ...
### 7.2 验收标准
- [ ] 标准1
- [ ] 标准2
### 7.3 检查清单
- [ ] 检查点1
- [ ] 检查点2
## 8. 变更管理
### 变更流程
1. 提出变更请求
2. 评估变更影响
3. 审批变更
4. 执行变更
5. 验证变更效果
## 附录
- 术语表
- 参考资料
- 历史记录
Best Practices
Planning Phase
- Start early: Plan as soon as possible after project initiation
- Full participation: Key personnel participate in planning
- Stay flexible: Plans should be adjustable
- Make assumptions explicit: Mark uncertain factors
Execution Phase
- Regular Review: Review plan execution weekly
- Timely Adjustment: Correct deviations promptly when found
- Transparent Communication: Keep information synchronized
- Focus on Risks: Continuously monitor risks
Closing Phase
- Complete Delivery: Ensure deliverables are complete
- Document Archiving: Organize project documents
- Experience Retrospective: Summarize lessons learned
- Knowledge Accumulation: Accumulate reusable methods
Working with Other Skills
This skill can be used in conjunction with the following skills:
- project-management: First do requirements analysis, then do execution planning
- task-management: Convert the plan into a task list
- code-development: Guidance during the technical implementation phase
- document-skills: Write project documentation
- time-management: Personal time management optimization
Precautions
- Planning Must Be Grounded: Based on data and analysis, not guesswork
- Leave Buffer: The plan should reserve contingency time
- Update Regularly: The plan should be updated as the project progresses
- Focus on Execution: Planning is for execution, not for perfection
- Team Consensus: The plan should reach consensus with the team
- Continuous Optimization: Continuously optimize the planning method based on actual conditions
Frequently Asked Questions
Q: How long does planning take?
A: A few hours for a simple project, and possibly several days for a complex project. The key is planning quality, not speed.
Q: Can the plan be changed?
A: Of course. A plan is living and needs to be adjusted according to actual conditions. The key is to control the impact of changes.
Q: How detailed should task breakdown be?
A: Generally, break tasks down to those that can be completed in 2-3 days. Too coarse and it is hard to track; too fine and management costs are high.
Q: How can the plan be ensured to be implemented?
A: Plan + execution + feedback form a closed loop. Review regularly, adjust promptly, and ensure the plan guides execution.