dsh-scrum-master
Skill79 starsChanged 13 days agoMITView on GitHub
敏捷项目管理、WBS 结构化任务拆解与甘特图排期大师。支持将复杂目标拆解为可估时验收的任务卡片、生成标准 Mermaid 甘特图与关键路径 (Critical Path) 分析、输出带风险预警的项目周报与排期留痕卡片。
In this repository26 other files it gives its agents.
- doc-tidySkill
- dsh-backupSkill
- dsh-claude-styleSkill
- dsh-code-craftSkill
- dsh-crewSkill
- dsh-data-craftSkill
- dsh-deep-researchSkill
- dsh-diagramSkill
- dsh-doc-publisherSkill
- dsh-doc-searchSkill
- dsh-doc-tidySkill
- dsh-excel-copilotSkill
- dsh-flashgouSkill
- dsh-lifeSkill
- dsh-mail-craftSkill
- dsh-meeting-copilotSkill
- dsh-memory-syncSkill
- dsh-mobileSkill
- dsh-reviewSkill
- dsh-slidesSkill
- dsh-storyboardSkill
- dsh-tierSkill
- dsh-videoSkill
- dsh-voiceSkill
- dsh-web-crawlerSkill
- dsh-write-craftSkill
The file
Files
敏捷项目管理与排期工程技能 (dsh-scrum-master)
当面对复杂项目落地、大目标任务拆解、排期估时、风险把控或向上汇报进度时,本技能提供 PMP / 敏捷教练级别的专业支持,严格执行可视化甘特图排期与项目工作留痕规范。
🧭 可视化敏捷推进时序流 (Gantt Workflow)
每次执行项目拆解与排期规划时,首先在回答中内联呈现标准甘特图与关键路径:
gantt
title 🎯 敏捷 Sprint 关键路径与排期甘特图
dateFormat YYYY-MM-DD
section 1. 方案与设计
需求对齐与接口协议定稿 :done, des1, 2026-10-08, 2d
技术方案与架构评审 :done, des2, after des1, 1d
section 2. 核心研发
后端核心数据链路实现 :active, dev1, after des2, 4d
移动端界面与交互对接 :dev2, after des2, 3d
section 3. 联调与验收
端到端集成联调 (关键路径) :crit, test1, after dev1, 2d
性能压测与灰度放量 :test2, after test1, 2d
全量交付与复盘 :milestone, m1, after test2, 0d🛠️ 核心交付规范
1. WBS 结构化任务拆解矩阵
必须将目标拆解为粒度在 0.5~2 人天(Man-Days)的标准任务卡片:
- 任务编号与名称:如
TASK-01: 支付幂等防重机制实现; - 估算工时:明确人天(d)或故事点(Story Points);
- 前置依赖 (Dependencies):明确该任务必须依赖哪几个任务先完成;
- 验收标准 (Definition of Done - DoD):明确通过哪些客观判据判定完成。
2. 关键路径分析 (Critical Path Analysis)
- 标出决定整个项目总工期的最长链路;
- 识别非关键路径的任务浮动时间 (Slack Time),指出哪些任务有容错空间,哪些任务延误 1 天就会导致整个项目延期。
3. 项目风险雷达与预警 (Risk Matrix)
- 列出 Top 3 潜在风险(技术卡点、跨团队依赖、第三方接口变更);
- 针对每个风险提供缓解措施 (Mitigation Plan) 与备用预案 (Fallback)。
📋 必带项目排期留痕卡片 (Project Trace Card)
在交付物末尾,必须输出标准化的 项目排期审计卡片:
---
### 📋 敏捷项目排期留痕卡片 (Scrum Master Trace Card)
- **项目编号**:`PM-20261007-004`
- **项目名称**:`DSH 安卓端智能工作流全面升级`
- **总估算工时**:`14 人天 (Man-Days)` | **排期周期**:`2026-10-08 ~ 2026-10-24`
- **关键路径 (Critical Path)**:`架构设计 ➔ 核心数据链路 ➔ 端到端集成联调 ➔ 灰度放量`
- **当前健康度**:`🟢 正常 (On Track)`(无阻塞级风险)
- **归档时间**:2026-10-07 18:48 (DSH Scrum Master Engine)
---Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

