faion-project-manager
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseEntry point:— invoke this skill for automatic routing to the appropriate domain./faion-net
入口点:— 调用此技能可自动路由至对应领域。/faion-net
PM Domain Skill (Orchestrator)
PM领域技能(编排器)
Communication: User's language. Docs/code: English.
沟通语言: 用户使用的语言。文档/代码:英文。
Purpose
目标
Orchestrates project management activities using PMBoK 7/8 framework. Coordinates two specialized sub-skills for comprehensive PM coverage.
基于PMBoK 7/8框架编排项目管理活动。协调两个专业子技能,实现全面的项目管理覆盖。
Context Discovery
上下文发现
Auto-Investigation
自动调查
Check for existing PM artifacts and project setup:
| Signal | How to Check | What It Tells Us |
|---|---|---|
| | SDD project structure |
| | Roadmap exists |
| | Project standards defined |
| Jira/Linear refs | | PM tool in use |
| Sprint folders | | Agile sprints used |
| Risk register | | Risk management in place |
Read existing artifacts:
- constitution.md for project scope and constraints
- roadmap.md for current plans
- Any existing sprint/planning docs
检查现有项目管理工件及项目配置:
| 信号 | 检查方式 | 说明信息 |
|---|---|---|
| | SDD项目结构 |
| | 存在路线图 |
| | 已定义项目标准 |
| Jira/Linear引用 | | 正在使用的PM工具 |
| Sprint文件夹 | | 采用敏捷Sprint模式 |
| 风险登记册 | | 已落实风险管理 |
读取现有工件:
- constitution.md:获取项目范围与约束条件
- roadmap.md:了解当前计划
- 任何现有的Sprint/规划文档
Discovery Questions
发现问题
Use to understand PM needs.
AskUserQuestion使用了解项目管理需求。
AskUserQuestionQ1: PM Approach
Q1:项目管理方法
yaml
question: "What project management approach do you prefer?"
header: "Approach"
multiSelect: false
options:
- label: "Agile (Scrum, Kanban)"
description: "Iterative, sprints, flexible scope"
- label: "Traditional (Waterfall, PMBoK)"
description: "Sequential, fixed scope, detailed planning"
- label: "Hybrid"
description: "Mix of agile and traditional"
- label: "Not sure / recommend"
description: "I'll suggest based on your project"Routing:
- "Agile" →
Skill(faion-pm-agile) - "Traditional" →
Skill(faion-pm-traditional) - "Hybrid" → Both skills as needed
- "Not sure" → Ask Q2 to determine
yaml
question: "你偏好哪种项目管理方法?"
header: "方法选择"
multiSelect: false
options:
- label: "Agile (Scrum, Kanban)"
description: "迭代式、Sprints、灵活范围"
- label: "Traditional (Waterfall, PMBoK)"
description: "顺序式、固定范围、详细规划"
- label: "Hybrid"
description: "敏捷与传统混合模式"
- label: "不确定 / 需要推荐"
description: "我会根据你的项目给出建议"路由规则:
- "Agile" →
Skill(faion-pm-agile) - "Traditional" →
Skill(faion-pm-traditional) - "Hybrid" → 根据需要调用两个技能
- "不确定" → 询问Q2来确定
Q2: Project Characteristics (if "Not sure")
Q2:项目特征(若选择“不确定”)
yaml
question: "What describes your project best?"
header: "Project"
multiSelect: false
options:
- label: "Requirements likely to change"
description: "User feedback, evolving product"
- label: "Requirements are fixed"
description: "Clear deliverables, contract"
- label: "Small team (1-5 people)"
description: "Lightweight process needed"
- label: "Large team / multiple teams"
description: "Coordination, dependencies"Recommendation:
- "Change" → Agile (Scrum or Kanban)
- "Fixed" → Traditional (WBS, schedule)
- "Small team" → Kanban or lightweight Scrum
- "Large team" → Scaled Agile or traditional PMBoK
yaml
question: "你的项目最符合以下哪种描述?"
header: "项目特征"
multiSelect: false
options:
- label: "需求可能会变更"
description: "用户反馈驱动、产品持续演进"
- label: "需求固定"
description: "交付物明确、基于合同"
- label: "小型团队(1-5人)"
description: "需要轻量化流程"
- label: "大型团队 / 多团队"
description: "需要协调管理、处理依赖关系"推荐方案:
- "需求可能变更" → Agile(Scrum或Kanban)
- "需求固定" → Traditional(WBS、进度计划)
- "小型团队" → Kanban或轻量化Scrum
- "大型团队" → 规模化敏捷或传统PMBoK
Q3: PM Task Type
Q3:PM任务类型
yaml
question: "What PM help do you need right now?"
header: "Task"
multiSelect: true
options:
- label: "Planning (scope, schedule, WBS)"
description: "Define what, when, how"
- label: "Team coordination (RACI, ceremonies)"
description: "Roles, meetings, communication"
- label: "Risk management"
description: "Identify and mitigate risks"
- label: "Progress tracking (EVM, metrics)"
description: "Monitor and report status"
- label: "Tool setup (Jira, Linear, etc.)"
description: "Configure PM tooling"Routing:
- "Planning" → wbs-creation, schedule-development
- "Team" → team-charter, raci-matrix, ceremonies
- "Risk" → risk-register, risk-response-planning
- "Progress" → earned-value-management, dashboards
- "Tool" → pm-tools-setup
yaml
question: "你当前需要哪方面的项目管理协助?"
header: "任务类型"
multiSelect: true
options:
- label: "规划(范围、进度、WBS)"
description: "定义内容、时间、方式"
- label: "团队协调(RACI、仪式)"
description: "角色、会议、沟通机制"
- label: "风险管理"
description: "识别并缓解风险"
- label: "进度跟踪(EVM、指标)"
description: "监控并报告状态"
- label: "工具配置(Jira、Linear等)"
description: "配置项目管理工具"路由规则:
- "规划" → wbs-creation, schedule-development
- "团队协调" → team-charter, raci-matrix, ceremonies
- "风险管理" → risk-register, risk-response-planning
- "进度跟踪" → earned-value-management, dashboards
- "工具配置" → pm-tools-setup
Q4: Current PM Maturity
Q4:当前PM成熟度
yaml
question: "What's your current PM setup?"
header: "Maturity"
multiSelect: false
options:
- label: "No formal process"
description: "Ad-hoc, need structure"
- label: "Basic process exists"
description: "Have backlog, need improvement"
- label: "Established process"
description: "Working well, need optimization"Context impact:
- "No formal" → Start with basics, don't overwhelm
- "Basic exists" → Build on what works, fill gaps
- "Established" → Optimize, metrics, continuous improvement
yaml
question: "你当前的项目管理配置处于什么阶段?"
header: "成熟度"
multiSelect: false
options:
- label: "无正式流程"
description: "临时应对,需要建立结构化流程"
- label: "已有基础流程"
description: "具备待办事项,需要优化"
- label: "流程已确立"
description: "运行良好,需要持续优化"上下文影响:
- "无正式流程" → 从基础开始,避免过度复杂
- "已有基础流程" → 基于现有流程构建,填补空白
- "流程已确立" → 优化流程、完善指标、持续改进
Architecture
架构
faion-project-manager (orchestrator)
|
+-> faion-project-manager:agile (28 methodologies)
| - Scrum, Kanban, SAFe ceremonies
| - PM tools (Jira, Linear, ClickUp, GitHub, etc.)
| - Dashboards, reporting, metrics
| - Team development, RACI
| - AI in PM, hybrid delivery
|
+-> faion-project-manager:traditional (22 methodologies)
- PMBoK knowledge areas
- Stakeholder management
- Planning (scope, schedule, cost, WBS)
- Risk management
- EVM, quality, change control
- Project closure, lessons learnedfaion-project-manager (orchestrator)
|
+-> faion-project-manager:agile (28种方法论)
| - Scrum, Kanban, SAFe ceremonies
| - PM工具(Jira, Linear, ClickUp, GitHub等)
| - 仪表板、报告、指标
| - 团队发展、RACI
| - AI在PM中的应用、混合交付
|
+-> faion-project-manager:traditional (22种方法论)
- PMBoK知识领域
- 干系人管理
- 规划(范围、进度、成本、WBS)
- 风险管理
- EVM、质量、变更控制
- 项目收尾、经验总结References
参考资料
| Reference | Content |
|---|---|
| ref-pmbok.md | PMBoK 7/8 overview, 8 domains, 12/6 principles |
| ref-CLAUDE.md | External resources, tools, certifications |
| 参考文档 | 内容 |
|---|---|
| ref-pmbok.md | PMBoK 7/8概述、8个绩效领域、12/6项原则 |
| ref-CLAUDE.md | 外部资源、工具、认证 |
Sub-Skills
子技能
faion-project-manager:agile (28 methodologies)
faion-project-manager:agile(28种方法论)
Use when:
- Planning sprints or ceremonies
- Selecting or setting up PM tools
- Building dashboards and reports
- Implementing agile/hybrid approaches
- Team development and roles
Key methodologies:
- Scrum/Kanban ceremonies
- Jira, Linear, ClickUp, GitHub Projects
- Dashboard setup, reporting
- Team development, RACI matrix
- AI in PM, hybrid delivery
Location:
~/.claude/skills/faion-project-manager:agile/适用场景:
- 规划Sprints或仪式
- 选择或配置PM工具
- 构建仪表板与报告
- 实施敏捷/混合方法
- 团队发展与角色定义
核心方法论:
- Scrum/Kanban仪式
- Jira、Linear、ClickUp、GitHub Projects
- 仪表板配置、报告
- 团队发展、RACI矩阵
- AI在PM中的应用、混合交付
位置:
~/.claude/skills/faion-project-manager:agile/faion-project-manager:traditional (22 methodologies)
faion-project-manager:traditional(22种方法论)
Use when:
- Planning project scope, schedule, cost
- Managing stakeholders
- Handling risks and uncertainty
- Tracking performance with EVM
- Closing projects and capturing lessons
Key methodologies:
- Stakeholder register and engagement
- Scope, WBS, schedule, cost, resources
- Risk register and management
- EVM, quality, change control
- Project closure, lessons learned
Location:
~/.claude/skills/faion-project-manager:traditional/适用场景:
- 规划项目范围、进度、成本
- 管理干系人
- 处理风险与不确定性
- 用EVM跟踪绩效
- 项目收尾与经验总结
核心方法论:
- 干系人登记册与参与管理
- 范围、WBS、进度、成本、资源
- 风险登记册与管理
- EVM、质量、变更控制
- 项目收尾、经验总结
位置:
~/.claude/skills/faion-project-manager:traditional/Decision Guide
决策指南
| Task Type | Sub-Skill | Examples |
|---|---|---|
| Agile Execution | faion-agile-pm | Sprint planning, standups, retros |
| Tool Selection | faion-agile-pm | Which PM tool? How to setup? |
| Reporting | faion-agile-pm | Dashboards, burn charts, velocity |
| Team Structure | faion-agile-pm | RACI, team development |
| Project Planning | faion-traditional-pm | Scope, WBS, schedule, cost |
| Stakeholders | faion-traditional-pm | Identify, analyze, engage |
| Risk Management | faion-traditional-pm | Risk register, responses |
| Performance | faion-traditional-pm | EVM (CPI, SPI, EAC) |
| Project Closure | faion-traditional-pm | Close, lessons learned, benefits |
| 任务类型 | 子技能 | 示例 |
|---|---|---|
| 敏捷执行 | faion-agile-pm | Sprint规划、站会、回顾会 |
| 工具选择 | faion-agile-pm | 选择哪种PM工具?如何配置? |
| 报告 | faion-agile-pm | 仪表板、燃尽图、速度指标 |
| 团队结构 | faion-agile-pm | RACI、团队发展 |
| 项目规划 | faion-traditional-pm | 范围、WBS、进度、成本 |
| 干系人管理 | faion-traditional-pm | 识别、分析、参与 |
| 风险管理 | faion-traditional-pm | 风险登记册、应对措施 |
| 绩效跟踪 | faion-traditional-pm | EVM(CPI、SPI、EAC) |
| 项目收尾 | faion-traditional-pm | 收尾、经验总结、收益确认 |
PMBoK 8 Overview
PMBoK 8概述
8 Performance Domains
8个绩效领域
| Domain | Sub-Skill |
|---|---|
| Stakeholder | faion-traditional-pm |
| Team | faion-agile-pm |
| Development Approach | faion-agile-pm |
| Planning | faion-traditional-pm |
| Project Work | faion-traditional-pm |
| Delivery | Both |
| Measurement | faion-traditional-pm (EVM) + faion-agile-pm (dashboards) |
| Uncertainty | faion-traditional-pm |
| 领域 | 子技能 |
|---|---|
| 干系人 | faion-traditional-pm |
| 团队 | faion-agile-pm |
| 交付方法 | faion-agile-pm |
| 规划 | faion-traditional-pm |
| 项目工作 | faion-traditional-pm |
| 交付 | 两者均可 |
| 度量 | faion-traditional-pm(EVM) + faion-agile-pm(仪表板) |
| 不确定性 | faion-traditional-pm |
12 Core Principles (PMBoK 7)
12项核心原则(PMBoK 7)
Stewardship, Team, Stakeholders, Value, Systems Thinking, Leadership, Tailoring, Quality, Complexity, Risk, Adaptability, Change.
管理 stewardship、团队、干系人、价值、系统思维、领导力、定制化、质量、复杂性、风险、适应性、变更。
Common Workflows
常见工作流
New Project
新项目启动
1. faion-traditional-pm: stakeholder-register
2. faion-agile-pm: raci-matrix
3. faion-traditional-pm: scope-management, wbs-creation
4. faion-traditional-pm: schedule-development, cost-estimation
5. faion-traditional-pm: risk-register
6. faion-agile-pm: pm-tools-overview (select tool)1. faion-traditional-pm: 干系人登记册
2. faion-agile-pm: RACI矩阵
3. faion-traditional-pm: 范围管理、WBS创建
4. faion-traditional-pm: 进度制定、成本估算
5. faion-traditional-pm: 风险登记册
6. faion-agile-pm: PM工具概述(选择工具)Sprint/Iteration
Sprint/迭代周期
1. faion-agile-pm: scrum-ceremonies (planning)
2. faion-agile-pm: dashboard-setup
3. faion-traditional-pm: earned-value-management (track)
4. faion-agile-pm: scrum-ceremonies (review, retro)1. faion-agile-pm: Scrum仪式(规划会)
2. faion-agile-pm: 仪表板配置
3. faion-traditional-pm: 挣值管理(跟踪)
4. faion-agile-pm: Scrum仪式(评审会、回顾会)Health Check
健康检查
1. faion-traditional-pm: earned-value-management
2. faion-traditional-pm: risk-management
3. faion-traditional-pm: stakeholder-engagement
4. faion-agile-pm: reporting-basics1. faion-traditional-pm: 挣值管理
2. faion-traditional-pm: 风险管理
3. faion-traditional-pm: 干系人参与
4. faion-agile-pm: 报告基础Integration Points
集成点
| Domain Skill | Integration |
|---|---|
| faion-sdd | Task planning uses PMBoK scheduling |
| faion-business-analyst | Requirements feed into scope |
| faion-product-manager | Roadmap aligns with schedule |
| faion-software-developer | Developer tools (GitHub, Linear) |
PM Domain Skill v4.0 - Orchestrator
2 sub-skills | 50 methodologies | PMBoK 7/8
| 领域技能 | 集成方式 |
|---|---|
| faion-sdd | 任务规划采用PMBoK进度管理 |
| faion-business-analyst | 需求输入至范围管理 |
| faion-product-manager | 路线图与进度计划对齐 |
| faion-software-developer | 开发者工具(GitHub、Linear)集成 |
PM领域技能 v4.0 - 编排器
2个子技能 | 50种方法论 | PMBoK 7/8