Project Path Planning and Execution Assistant
Core Positioning
This is a skill focused on project execution planning, which helps you systematically plan the project path from idea to implementation, and ensure the project is delivered on time and with high quality. Different from product requirement document (PRD) analysis, this skill pays more attention to how to do it and how to do it well.
Applicable Scenarios
Project Initiation Phase
- "I want to build an e-commerce mini-program, help me make a plan"
- "My boss asked me to take charge of a new project, where should I start?"
- "How long will it take to complete this requirement roughly?"
Project Planning Phase
- "Help me decompose the tasks of this project"
- "These functions have dependencies, how to arrange the order?"
- "How to complete this project within 3 months?"
Project Execution Phase
- "The project is delayed, how to adjust the plan?"
- "Help me check if this task decomposition is reasonable"
- "How to track the project progress of the team?"
Project Closing Phase
- "The project is about to be delivered, what are the items on the check list?"
- "How to do a project review?"
- "How to accumulate project experience?"
Usage Method
Quick Start
Directly describe your project situation:
"帮我规划一个项目：开发一个团队协作工具，团队3个人，2个月后要上线"
"这是我们产品的功能清单，帮我做个项目计划"
"项目需求发生了变更，帮我重新规划一下路径"
Provide Detailed Information
The more information you provide, the more accurate the plan will be:
Basic Information:
- Project name and objectives
- Team size and role division
- Time constraints and key milestones
- Budget and resource limits
Project Background (Optional):
- Whether there is an existing system that needs to be connected
- Technical stack requirements or restrictions
- Relevant historical project experience
Reference Documents (Optional):
- Upload requirement 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 Disassembly
Project Background Analysis:
- Understand the core objectives and value of the project
- Identify key stakeholders
- Clarify project boundaries and constraints
Task Decomposition (WBS):
- Decompose the project into manageable modules
- Identify dependencies between modules
- Estimate the workload of each task
Priority Sorting:
- Sort by business value
- Sort by dependency relationship
- Sort by risk level
2. Milestone and Time Planning
Milestone Setting:
- Define clear phased objectives
- Set verifiable deliverables
- Reserve buffer time
Timeline Planning:
- Draw the project timeline
- Plan the critical path
- Balance resource allocation
Schedule Arrangement:
- Arrange parallel tasks reasonably
- Avoid excessive concentration of resources
- Reserve emergency time
3. Team and Resource Planning
Roles and Responsibilities:
- Clarify the roles of team members
- Define responsibility boundaries
- Establish reporting relationships
Resource Allocation:
- Evaluate human resource requirements
- Plan technical/tool resources
- Budget and time resources
Collaboration Mechanism:
- Determine communication frequency and methods
- Establish a synchronization mechanism
- 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:
- Evaluate the probability of risk occurrence
- Evaluate the impact degree of risks
- Determine risk priority
Response Strategy:
- Formulate preventive measures
- Prepare emergency plans
- Assign risk responsible persons
5. Quality Assurance Planning
Quality Standards:
- Define quality objectives and indicators
- Establish acceptance criteria
- Determine quality check points
Test Strategy:
- Plan test types and scope
- Arrange test time
- Define test standards
Review Mechanism:
- Plan review nodes
- Define review standards
- Establish a closed feedback loop
Output Results
After the planning is completed, you will get the following results:
Project Overview
- Project background and objectives
- Project scope and boundaries
- Key constraints
Task Decomposition
- Work Breakdown Structure (WBS)
- Task dependency diagram
- Task priority sorting
Time Planning
- Project milestones
- Detailed schedule
- Critical path identification
Team Collaboration
- Role division
- Communication plan
- Collaboration tool recommendation
Risk Register
- List of identified risks
- Risk assessment matrix
- Response strategies and pre-plans
Quality Assurance
- Quality standards
- Acceptance criteria
- Check list
Project Planning Template
Quick Planning Template
markdown
# [项目名称] 规划方案
## 项目概述
- **项目目标**: [一句话描述项目要实现什么]
- **交付物**: [项目最终交付什么]
- **时间约束**: [截止日期或时间范围]
- **团队规模**: [多少人参与]
## 核心任务
### 阶段一：[名称]
- [ ] 任务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
markdown
# 项目规划文档
## 1. 项目定义
### 1.1 项目背景
[项目产生的背景和原因]
### 1.2 项目目标
- **主要目标**: [核心目标]
- **次要目标**: [辅助目标]
- **成功标准**: [如何判断项目成功]
### 1.3 项目范围
- **包含范围**: [做的是什么]
- **排除范围**: [不做什么]
- **边界条件**: [什么情况下算完成]
## 2. 任务分解
### 2.1 工作分解结构(WBS)
项目
├── 模块1
│ ├── 任务1.1
│ ├── 任务1.2
│ └── 任务1.3
├── 模块2
│ ├── 任务2.1
│ └── 任务2.2
└── 模块3
├── 任务3.1
└── 任务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 as early as possible: Plan as soon as possible after the project starts
- Full participation: Key personnel participate in the planning
- Stay flexible: The plan should be adjustable
- Clarify assumptions: Mark uncertain factors
Execution Phase
- Regular review: Review the implementation of the plan every week
- Adjust in time: Correct deviations as soon as they are found
- Transparent communication: Keep information synchronized
- Focus on risks: Continuously monitor risks
Closing Phase
- Complete delivery: Ensure that the deliverables are complete
- Document archiving: Organize project documents
- Experience review: Summarize experiences and lessons
- Knowledge precipitation: Precipitate reusable methods
Cooperation with Other Skills
This skill can be used in conjunction with the following skills:
- project-management: First do requirement analysis, then do execution planning
- task-management: Convert the plan into a task list
- code-development: Guidance in the technical implementation stage
- document-skills: Write project documents
- time-management: Optimize personal time management
Notes
- The plan should be based on evidence: Based on data and analysis, not random assumptions
- Reserve buffer: Reserve emergency time in the plan
- 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 a consensus with the team
- Continuous optimization: Continuously optimize the planning method according to the actual situation
Frequently Asked Questions
Q: How long does planning take?
A: A few hours for simple projects, and a few days for complex projects. The key is the quality of planning, not speed.
Q: Can the plan be changed?
A: Of course. The plan is dynamic and needs to be adjusted according to the actual situation. The key is to control the impact of changes.
Q: How detailed should the task decomposition be?
A: Generally, it is appropriate to decompose into tasks that can be completed in 2-3 days. Too coarse is difficult to track, too fine leads to high management costs.
Q: How to ensure the implementation of the plan?
A: Planning + execution + closed feedback loop. Review regularly, adjust in time, and ensure that the plan guides execution.