关于 cwm-doc-generation
面向 ServiceNow 项目与组合管理人员的技能,利用项目、任务、风险和资源数据生成状态报告、利益相关方沟通及组合摘要。流程涵盖数据检索、健康度分析和按受众组织内容。
主要功能
- 01生成项目状态报告
- 02汇总里程碑与任务进度
- 03整理风险、问题和资源数据
- 04按受众撰写沟通内容
- 05生成项目组合摘要
适用场景
- 01准备每周或每月项目更新
- 02向高管汇报项目组合健康度
- 03整理风险与问题摘要
- 04制作会议用项目进展材料
MCP 相关
该技能通过 ServiceNow MCP 工具检索项目、任务、风险和资源记录,也可创建或保存报告相关记录。
安装
复制下面的命令,在终端中运行。
$
npx skills add https:/ / github.com/ happy-technologies-llc/ happy-platform-skills --skill cwm-doc-generation安装后在 Claude Code 中输入/cwm-doc-generation确认已加载。
详细介绍
CWM 文档生成
概述
此技能介绍如何根据 ServiceNow 项目数据生成全面的协作工作管理(CWM)文档:
- 创建自动化项目状态报告,涵盖里程碑进度、预算和时间线健康状况
- 生成风险摘要,包含影响评估和缓解计划
- 根据受众(高管、赞助人、团队)定制利益相关者沟通内容
- 构建投资组合级仪表板,汇总多个项目的健康指标
- 从任务数据、资源分配和活动历史记录中提取项目洞察
- 生成可用于会议的项目更新演示文稿
适用场景: 准备每周/每月状态报告、向利益相关者传达项目健康状况、为领导层汇总投资组合状态,或生成风险和问题摘要时。
前提条件
- 角色:
project_manager、program_manager、portfolio_manager或admin - 插件:
com.snc.project_management(项目投资组合管理)或 CWM 工作区 - 访问权限: 对
pm_project、pm_project_task、planned_task、risk、issue、pm_resource_plan表具有读取权限 - 数据: 已填充任务、里程碑和状态数据的活动项目
- 相关技能: 用于任务分解的
spm/cwm-tasks-generation,用于分析的spm/project-insights
流程
第 1 步:检索项目概览数据
提取包含关键健康指标的核心项目记录。
MCP 方式:
Tool: SN-Get-Record
Parameters:
table_name: pm_project
sys_id: [PROJECT_SYS_ID]
fields: sys_id,number,short_description,description,state,phase,priority,percent_complete,planned_start_date,planned_end_date,actual_start_date,actual_end_date,budget_cost,actual_cost,project_manager,sponsor,portfolio,program,health,schedule_health,cost_health,scope_health,resource_health
REST 方式:
GET /api/now/table/pm_project/[PROJECT_SYS_ID]
?sysparm_fields=sys_id,number,short_description,description,state,phase,priority,percent_complete,planned_start_date,planned_end_date,actual_start_date,actual_end_date,budget_cost,actual_cost,project_manager,sponsor,portfolio,program,health,schedule_health,cost_health,scope_health,resource_health
&sysparm_display_value=true
第 2 步:检索里程碑和任务进度
获取里程碑完成状态和任务进度指标。
MCP 方式:
Tool: SN-Query-Table
Parameters:
table_name: pm_project_task
query: project=[PROJECT_SYS_ID]^milestone=true^ORDERBYplanned_start_date
fields: sys_id,number,short_description,state,percent_complete,planned_start_date,planned_end_date,actual_start_date,actual_end_date,assigned_to
limit: 50
Tool: SN-Query-Table
Parameters:
table_name: pm_project_task
query: project=[PROJECT_SYS_ID]
fields: sys_id,state,percent_complete,priority
limit: 500
REST 方式:
GET /api/now/table/pm_project_task
?sysparm_query=project=[PROJECT_SYS_ID]^milestone=true^ORDERBYplanned_start_date
&sysparm_fields=sys_id,number,short_description,state,percent_complete,planned_start_date,planned_end_date,actual_start_date,actual_end_date,assigned_to
&sysparm_display_value=true
第 3 步:检索风险和问题
提取与项目相关的活动风险和问题。
MCP 方式:
Tool: SN-Query-Table
Parameters:
table_name: risk
query: task=[PROJECT_SYS_ID]^state!=closed
fields: sys_id,number,short_description,category,probability,impact,risk_score,response,state,assigned_to,mitigation_plan
limit: 30
Tool: SN-Query-Table
Parameters:
table_name: issue
query: task=[PROJECT_SYS_ID]^state!=closed
fields: sys_id,number,short_description,priority,state,assigned_to,resolution,sys_created_on
limit: 30
REST 方式:
GET /api/now/table/risk
?sysparm_query=task=[PROJECT_SYS_ID]^state!=closed
&sysparm_fields=sys_id,number,short_description,category,probability,impact,risk_score,response,state,assigned_to,mitigation_plan
&sysparm_display_value=true
GET /api/now/table/issue
?sysparm_query=task=[PROJECT_SYS_ID]^state!=closed
&sysparm_fields=sys_id,number,short_description,priority,state,assigned_to,resolution,sys_created_on
&sysparm_display_value=true
第 4 步:检索资源分配数据
获取资源计划信息,以了解容量和利用率。
MCP 方式:
Tool: SN-Query-Table
Parameters:
table_name: pm_resource_plan
query: project=[PROJECT_SYS_ID]^state=active
fields: sys_id,resource,role,planned_hours,actual_hours,remaining_hours,start_date,end_date,utilization
limit: 50
REST 方式:
GET /api/now/table/pm_resource_plan
?sysparm_query=project=[PROJECT_SYS_ID]^state=active
&sysparm_fields=sys_id,resource,role,planned_hours,actual_hours,remaining_hours,start_date,end_date,utilization
&sysparm_display_value=true
第 5 步:生成项目状态报告
将所有数据汇编成结构化的状态报告。
=== PROJECT STATUS REPORT ===
Report Date: [current_date]
Project: [number] - [short_description]
Project Manager: [project_manager]
Phase: [phase] | State: [state]
OVERALL HEALTH: [health_indicator]
Schedule: [schedule_health] | Cost: [cost_health]
Scope: [scope_health] | Resources: [resource_health]
PROGRESS SUMMARY:
Percent Complete: [percent_complete]%
Planned Timeline: [planned_start] - [planned_end]
Actual Timeline: [actual_start] - [projected_end]
Schedule Variance: [days ahead/behind]
BUDGET STATUS:
Budget: $[budget_cost]
Actual Spend: $[actual_cost]
Remaining: $[budget - actual]
Cost Variance: [percentage]% [over/under]
MILESTONE STATUS:
| Milestone | Planned Date | Status | Variance |
|-----------|-------------|--------|----------|
| [name] | [date] | [on-track/at-risk/complete/late] | [days] |
| [name] | [date] | [status] | [days] |
TASK METRICS:
Total Tasks: [count] | Complete: [count] | In Progress: [count]
Overdue Tasks: [count] | Blocked: [count]
RISKS ([count] active):
| Risk | Probability | Impact | Score | Response |
|------|------------|--------|-------|----------|
| [description] | [H/M/L] | [H/M/L] | [score] | [mitigate/accept/transfer] |
ISSUES ([count] open):
| Issue | Priority | Owner | Status |
|-------|----------|-------|--------|
| [description] | [P1-P4] | [name] | [investigating/resolving] |
KEY ACCOMPLISHMENTS (This Period):
- [Accomplishment 1]
- [Accomplishment 2]
PLANNED ACTIVITIES (Next Period):
- [Activity 1]
- [Activity 2]
DECISIONS NEEDED:
- [Decision 1 with context]
第 6 步:生成执行摘要
创建简洁的高管级沟通内容。
=== EXECUTIVE SUMMARY ===
Project: [name]
Status: [GREEN/YELLOW/RED]
HEADLINE: [One-sentence project status]
KEY METRICS:
- Progress: [%] complete ([ahead/behind] schedule by [days])
- Budget: $[actual] of $[budget] spent ([%] utilized)
- Next Milestone: [name] due [date] - [status]
TOP RISKS:
1. [Risk description] - Mitigation: [action]
2. [Risk description] - Mitigation: [action]
DECISIONS REQUIRED:
1. [Decision needed with recommendation]
FORECAST: [Project on track for [date] completion / Recommend [action] to recover schedule]
第 7 步:生成利益相关者沟通内容
针对不同受众定制沟通内容。
赞助人更新:
Subject: [Project Name] - Status Update [Date]
Dear [Sponsor Name],
[One paragraph summary of project health and progress]
Key highlights this period:
- [Highlight 1]
- [Highlight 2]
Items requiring your attention:
- [Decision or escalation needed]
Next milestone: [name] targeted for [date].
Full status report attached for reference.
团队更新:
Subject: [Project Name] - Weekly Update [Date]
Team,
Progress this week:
- [Completed item 1]
- [Completed item 2]
Focus for next week:
- [Priority 1] - Owner: [name]
- [Priority 2] - Owner: [name]
Blockers:
- [Blocker description] - Need: [what is needed]
Reminders:
- [Upcoming deadline or meeting]
第 8 步:生成投资组合摘要
用于多个项目的投资组合级报告。
MCP 方式:
Tool: SN-Query-Table
Parameters:
table_name: pm_project
query: portfolio=[PORTFOLIO_SYS_ID]^state=active
fields: sys_id,number,short_description,health,percent_complete,schedule_health,cost_health,budget_cost,actual_cost,planned_end_date,project_manager
limit: 50
=== PORTFOLIO STATUS SUMMARY ===
Portfolio: [name]
Report Date: [date]
Active Projects: [count]
HEALTH OVERVIEW:
Green: [count] | Yellow: [count] | Red: [count]
| Project | Health | Progress | Schedule | Budget | PM |
|---------|--------|----------|----------|--------|-----|
| [name] | [G/Y/R] | [%] | [on-track/late] | [$actual/$budget] | [name] |
PORTFOLIO BUDGET:
Total Budget: $[sum]
Total Spend: $[sum]
Overall Variance: [%]
ATTENTION REQUIRED:
- [Project X]: [issue requiring attention]
- [Project Y]: [risk or escalation]
工具使用
| 工具 | 用途 | 使用时机 |
|---|---|---|
| SN-Query-Table | 检索项目任务、风险、问题和资源 | 为报告收集数据 |
| SN-Get-Record | 获取详细的项目记录 | 检索核心项目数据 |
| SN-Natural-Language-Search | 根据自然语言描述查找项目 | 探索性查找项目 |
| SN-Create-Record | 在 ServiceNow 中创建状态报告记录 | 保存生成的报告 |
最佳实践
- 按周自动生成报告,以保持一致性
- 先呈现健康指标——利益相关者希望一眼了解状态
- 根据受众调整内容深度——高管需要摘要,团队需要详细信息
- 突出差异——重点关注与计划的偏差,而非复述计划
- 包含可执行事项——每份报告都应明确后续步骤或所需决策
- 采用一致的格式——在整个投资组合中统一报告模板
- 跟踪报告历史——保留状态报告记录,以便进行趋势分析
- 验证数据时效性——生成报告前,确保任务和里程碑数据是最新的
- 标记长期未更新的项目——突出显示过去 2 周内没有活动的项目
- 包含预测——始终展望未来,而不只是回顾过去
故障排查
| 问题 | 原因 | 解决方法 |
|---|---|---|
| 健康指标为空白 | 未配置或未运行健康度计算 | 触发项目健康度重新计算;检查健康规则配置 |
| 缺少里程碑日期 | 任务未标记为里程碑 | 确认关键项目任务已设置 milestone=true |
| 预算数据为零 | 项目记录中未填写预算字段 | 检查 budget_cost 和 actual_cost 字段;也可能使用单独的财务表 |
| 资源数据不完整 | 未创建资源计划或未关联资源计划 | 确认项目存在 pm_resource_plan 记录 |
| 未计算风险分数 | 尚未完成风险评估 | 确保风险记录中已填写概率和影响字段 |
| 项目组合查询未返回项目 | 项目未关联到项目组合 | 检查项目记录中的 portfolio 引用字段 |
示例
示例 1:每周状态报告
**场景:**为 ERP 实施项目生成每周状态报告。
Tool: SN-Get-Record
Parameters:
table_name: pm_project
sys_id: abc123def456
fields: number,short_description,health,percent_complete,schedule_health,cost_health,budget_cost,actual_cost,planned_end_date
生成的报告:
PROJECT STATUS - PRJ0010234: ERP Phase 2 Implementation
Week of March 15, 2026 | Health: YELLOW
Progress: 62% complete (target: 68%) - 6% behind plan
Budget: $1.2M of $2.0M spent (60%) - on track
Schedule: 8 business days behind due to vendor delay
MILESTONES:
- Data Migration Complete: Mar 10 - DONE
- UAT Start: Mar 22 - AT RISK (dependency on data validation)
- Go-Live: Apr 15 - AT RISK (cascading delay)
ACTION NEEDED: Approve additional vendor resources to recover schedule ($45K)
示例 2:高管项目组合简报
**场景:**生成月度项目组合摘要,供 CIO 审阅。
PORTFOLIO: Digital Transformation 2026
12 Active Projects | Budget: $8.5M
Summary: 8 Green, 3 Yellow, 1 Red
Overall Portfolio Health: YELLOW
RED PROJECT: Cloud Migration Phase 3
- 3 weeks behind schedule
- Key risk: Legacy system dependencies
- Recommendation: Extend timeline by 2 weeks, add integration resources
BUDGET: $3.2M spent of $8.5M (38%) - on track for year
相关技能
spm/cwm-tasks-generation- 根据需求生成任务分解spm/project-insights- 项目分析与趋势分析spm/planning-summarization- 总结项目规划数据spm/agile-story-generation- 为项目工作生成敏捷用户故事spm/acceptance-criteria- 为交付物定义验收标准
评论
支持 Markdown