mcpField
P
project-manager

project-manager

github.com/borghei生产力1.0k54 次安装6 天前更新
代码仓库

关于 project-manager

面向项目经理和团队的项目管理技能,涵盖规划、进度、资源、风险、预算和利益相关方沟通,并提供模板与脚本,用于组织交付过程。

主要功能

  1. 01制定项目章程与工作分解
  2. 02规划进度和关键路径
  3. 03记录并分析项目风险
  4. 04管理利益相关方沟通
  5. 05生成时间线与状态报告

适用场景

  1. 01拆解项目范围并安排阶段任务
  2. 02跟踪风险、负责人及缓解措施
  3. 03准备定期项目状态报告

安装

复制下面的命令,在终端中运行。

$npx skills add https://github.com/borghei/claude-skills --skill project-manager

安装后在 Claude Code 中输入/project-manager确认已加载。

详细介绍

项目经理

提供专家级项目管理,助力项目成功交付。

核心能力

  • 项目规划
  • 范围管理
  • 时间线与进度安排
  • 资源管理
  • 风险管理
  • 利益相关者沟通
  • 预算管理
  • 团队领导

项目规划

项目章程模板
# Project Charter: [Project Name]

## Project Overview
- Name: [Project Name]
- Sponsor: [Name]
- Project Manager: [Name]
- Start Date: [Date]
- Target End Date: [Date]

## Business Case
[Why are we doing this project?]

## Objectives
1. [Objective 1]
2. [Objective 2]
3. [Objective 3]

## Scope

### In Scope
- [Item 1]
- [Item 2]

### Out of Scope
- [Item 1]
- [Item 2]

## Success Criteria
- [Criterion 1]: [Measure]
- [Criterion 2]: [Measure]

## Key Stakeholders
| Name | Role | Interest | Influence |
|------|------|----------|-----------|
| [Name] | [Role] | [H/M/L] | [H/M/L] |

## High-Level Timeline
| Phase | Start | End | Key Deliverables |
|-------|-------|-----|------------------|
| Initiation | [Date] | [Date] | Charter, team |
| Planning | [Date] | [Date] | Plan, WBS |
| Execution | [Date] | [Date] | Deliverables |
| Closure | [Date] | [Date] | Handoff, lessons |

## Budget
- Estimated: $[X]
- Contingency: [X]%

## Risks
| Risk | Impact | Probability | Mitigation |
|------|--------|-------------|------------|
| [Risk] | H/M/L | H/M/L | [Action] |

## Approvals
| Name | Role | Signature | Date |
|------|------|-----------|------|
| | | | |
工作分解结构
PROJECT
├── Phase 1: Discovery
│   ├── 1.1 Requirements gathering
│   │   ├── 1.1.1 Stakeholder interviews
│   │   └── 1.1.2 Requirements documentation
│   └── 1.2 Technical assessment
│       ├── 1.2.1 Architecture review
│       └── 1.2.2 Integration analysis
├── Phase 2: Design
│   ├── 2.1 Solution design
│   └── 2.2 Design review
├── Phase 3: Build
│   ├── 3.1 Development
│   ├── 3.2 Testing
│   └── 3.3 Documentation
├── Phase 4: Deploy
│   ├── 4.1 Deployment preparation
│   ├── 4.2 Go-live
│   └── 4.3 Hypercare
└── Phase 5: Close
    ├── 5.1 Handoff
    └── 5.2 Lessons learned

进度管理

甘特图结构
Task                    | W1 | W2 | W3 | W4 | W5 | W6 | W7 | W8 |
------------------------|----|----|----|----|----|----|----|----|
Phase 1: Discovery      |████|████|    |    |    |    |    |    |
  Requirements          |████|    |    |    |    |    |    |    |
  Technical assessment  |    |████|    |    |    |    |    |    |
Phase 2: Design         |    |████|████|    |    |    |    |    |
  Solution design       |    |████|    |    |    |    |    |    |
  Design review         |    |    |████|    |    |    |    |    |
Phase 3: Build          |    |    |    |████|████|████|    |    |
  Development           |    |    |    |████|████|    |    |    |
  Testing               |    |    |    |    |████|████|    |    |
Phase 4: Deploy         |    |    |    |    |    |    |████|    |
Phase 5: Close          |    |    |    |    |    |    |    |████|
关键路径
START → [A:5d] → [B:3d] → [C:4d] → [E:2d] → END
              ↘ [D:2d] ↗

Critical Path: A → B → C → E (14 days)
Float on D: 2 days
会议安排
会议频率时长参会者目的
每日站会每日15 min团队状态、阻碍
每周状态会议每周30 min团队 + PM进度回顾
指导委员会会议每两周60 min赞助方决策、升级处理
回顾会议阶段结束时60 min团队改进

风险管理

风险登记册
ID风险类别概率影响分值负责人缓解措施状态
R1[描述]技术H/M/LH/M/L[1-25][姓名][措施]未处理
风险矩阵
              │ Low Impact │ Medium │ High Impact
──────────────┼────────────┼────────┼────────────
High Prob     │ Medium     │ High   │ Critical
Medium Prob   │ Low        │ Medium │ High
Low Prob      │ Low        │ Low    │ Medium
风险应对策略

威胁:

  • 规避:消除威胁
  • 缓解:降低发生概率或影响
  • 转移:转交第三方处理
  • 接受:承认并监控

机遇:

  • 利用:确保机遇得以实现
  • 增强:提高发生概率
  • 共享:与他人合作
  • 接受:若机遇出现,则加以利用

状态报告

状态报告模板
# Project Status Report
## [Project Name] - [Date]

### Overall Status: 🟢 Green / 🟡 Yellow / 🔴 Red

### Executive Summary
[2-3 sentences on overall progress]

### Key Metrics
| Metric | Target | Actual | Status |
|--------|--------|--------|--------|
| Schedule | On time | +2 days | 🟡 |
| Budget | $100K | $95K | 🟢 |
| Scope | 100% | 90% | 🟢 |
| Quality | 95% pass | 97% | 🟢 |

### Accomplishments This Period
- [Accomplishment 1]
- [Accomplishment 2]

### Planned Next Period
- [Plan 1]
- [Plan 2]

### Issues
| Issue | Impact | Owner | Target Date | Status |
|-------|--------|-------|-------------|--------|
| [Issue] | [Impact] | [Name] | [Date] | Open |

### Risks
| Risk | Impact | Probability | Mitigation |
|------|--------|-------------|------------|
| [Risk] | [H/M/L] | [H/M/L] | [Action] |

### Decisions Needed
- [Decision 1]: [Options]

### Budget Summary
- Approved: $[X]
- Spent: $[Y]
- Remaining: $[Z]
- Forecast: $[W]

利益相关者管理

RACI 矩阵
活动PM赞助方技术负责人团队
需求ACRI
设计AIRC
开发AICR
测试AICR
上线RACI

R = 负责执行,A = 最终负责,C = 协商,I = 知会

沟通计划
利益相关者信息频率方式负责人
赞助方状态、决策每周邮件、会议PM
团队任务、阻碍每日站会PM
用户进展、培训每两周新闻简报PM

变更管理

变更请求模板
# Change Request: [CR-XXX]

## Request Details
- Submitted by: [Name]
- Date: [Date]
- Priority: High/Medium/Low

## Change Description
[What is being requested?]

## Business Justification
[Why is this change needed?]

## Impact Analysis
- Schedule: [Impact]
- Budget: [Impact]
- Scope: [Impact]
- Resources: [Impact]

## Options
1. [Option 1]: [Pros/Cons]
2. [Option 2]: [Pros/Cons]
3. [Option 3]: [Pros/Cons]

## Recommendation
[Recommended approach]

## Approval
| Role | Name | Decision | Date |
|------|------|----------|------|
| PM | | | |
| Sponsor | | | |

参考资料

  • references/planning.md - 规划模板
  • references/risk_management.md - 风险框架
  • references/communication.md - 沟通模板
  • references/agile_pm.md - 敏捷项目管理

脚本

# Project timeline generator
python scripts/timeline_gen.py --wbs wbs.yaml --output gantt.html

# Risk analyzer
python scripts/risk_analyzer.py --register risks.csv

# Status report generator
python scripts/status_report.py --project "Project Name" --period weekly

# Resource planner
python scripts/resource_plan.py --team team.yaml --tasks tasks.csv

评论

支持 Markdown