菜单
Diagnose why delivery is unpredictable using flow + DORA as system signals, find the constraint, and fix it — never by velocity-quota'ing people. Reach for this when dates keep slipping.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/mcorbett51090/RavenClaude --skill improve-team-flow命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | improve-team-flow |
| description | Diagnose why delivery is unpredictable using flow + DORA as system signals, find the constraint, and fix it — never by velocity-quota'ing people. Reach for this when dates keep slipping. |
Measure flow and outcomes, never lines or commits — and never rank a person by a velocity metric (§3 #3).
Pull lead time, WIP, change-fail, and MTTR as system signals with a baseline (§3 #3). A signal without a window + baseline is just a number.
High WIP / context-switching? Hidden rework? Blocked dependencies? Estimation/scope churn? Traverse Tree 2 to localize the constraint.
Limit WIP and shrink batch size (Little's Law); make dependencies visible; tighten estimation hygiene. More pressure on a leaking process wastes the team.
If the candidate fix is "push harder," STOP — that's a velocity crackdown, not a system fix (§3 #3). Check on-call/burnout load with oncall-load.
A flow diagnosis with the constraint named and a sustainable fix, owners + dates attached. Route the people/burnout impact to people-and-growth-manager, tech-debt-as-constraint to technical-health-manager.