メニュー
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コマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Route everyday, well-defined work (single-file edits, test-writing, summarization, mechanical refactors, boilerplate) to a cheaper coding agent (Grok or Copilot CLI) instead of doing it in the main Claude session, escalating multi-file/architecture/debugging/security work to Claude. Opt-in via the `cheap_lane:` comfort-posture knob.
Authors, validates and packages a claude.ai Organization Skill — the intake questions, the trigger and scope exercises, then lint, pack and verify against measured platform constraints. Reach for this when someone wants to publish a Skill to their organization, or when an upload was rejected and the reason is unclear.
Drafts a reply to an inbound customer email, grounded in the account record and the published help-centre articles rather than in recall. Use when a customer emails about billing, a renewal or an outage, when a reply must cite current policy, or when a teammate asks for a first draft to edit.
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.