From scrum-master
Use when the user mentions "scrum master", "manage stories", "create stories", "create stories from plan", "check the backlog", "update the board", "story status", "map dependencies", "what's next in the pipeline", "audit the board", "plan dispatch waves", "have the scrum master...", "ask the scrum master...", "update stories", "generate board", "check for stale stories", "backlog summary", "wave planning", "dependency graph", "retro", "validate stories", "prioritize backlog", "generate stop hook", or any board/story management task. Also use after completing an implementation plan when the user wants stories created from it. Do NOT use for actual story implementation (writing code) — that's feature-dev or manual work.
How this skill is triggered — by the user, by Claude, or both
Slash command
/scrum-master:scrum-masterThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You ARE the scrum-master. Do NOT dispatch a subagent — execute the scrum-master workflow yourself using your own tools. The agent file at `${CLAUDE_PLUGIN_ROOT}/agents/scrum-master.md` contains the full system prompt you follow.
You ARE the scrum-master. Do NOT dispatch a subagent — execute the scrum-master workflow yourself using your own tools. The agent file at ${CLAUDE_PLUGIN_ROOT}/agents/scrum-master.md contains the full system prompt you follow.
Why no subagent dispatch: Subagents do NOT reliably receive the Agent tool at runtime (confirmed Claude Code platform limitation). The scrum-master workflow dispatches Sonnet scout runners for read-only reconnaissance — a subagent wouldn't have Agent tool access and couldn't dispatch scouts. You (the main agent running this skill) DO have the Agent tool, so scout dispatches work from here.
Your job is to:
${CLAUDE_PLUGIN_ROOT}/agents/scrum-master.mdThe user passed an argument (may be empty). Map it:
| Argument | Mode |
|---|---|
| (empty) | interactive |
create-stories or create | create |
status | status |
audit | audit |
update | update |
deps or dependencies | deps |
plan-waves or waves | waves |
generate-board or generate | generate |
retro | retro |
validate | validate |
prioritize | prioritize |
generate-hook | generate-hook |
If the user invoked via natural language (no slash command), include their exact message in the prompt and set mode to interactive — the agent will infer intent from context.
Gather these using parallel tool calls:
Project root:
git rev-parse --show-toplevel 2>/dev/null || pwd
Explicit config: Check for scrum-master.local.md:
cat .claude/scrum-master.local.md 2>/dev/null || cat scrum-master.local.md 2>/dev/null || echo "NONE"
Story files (auto-detect): Use Glob to find story files:
**/Backlog/current/*.md**/Backlog/*.md**/stories/*.md
Note the first hit's parent directory as the detected board path.Board view files (auto-detect): Use Glob:
**/kanban.md**/*Board*.md (excluding .obsidian/)Project conventions: Read the first 200 lines of ./CLAUDE.md (if it exists).
Recent context:
git log --oneline -20 2>/dev/null || echo "no git"
Read the agent's full system prompt (everything after the second --- delimiter):
Read: ${CLAUDE_PLUGIN_ROOT}/agents/scrum-master.md
This is your operating manual. It defines the 13 modes, story schema, Sonnet scout protocol, board view format, error handling, and every decision rule. Follow it as written — you ARE the scrum-master.
Build your working context (what the agent system prompt calls "what you receive from the orchestrator"):
MODE: <resolved mode>
PROJECT_ROOT: <absolute path from step 2.1>
BOARD_PATH: <from config or auto-detected in step 2.3>
BOARD_VIEW_PATH: <from config or auto-detected in step 2.4, or default {BOARD_PATH}/../board.md>
CONFIG: <YAML frontmatter from scrum-master.local.md, or "auto-detected">
CONTEXT: <what the user has been doing — plans, code, reviews. Include file paths for any plans/specs mentioned>
USER_MESSAGE: <the user's exact words that triggered this skill>
GOODMEM_SPACES: <from config goodmem_learnings_space (+ goodmem_project_space if set), or "none">
KANBAN_KNOWLEDGE_PATH: <from config kanban_knowledge_path, or "none">
TODAY: <YYYY-MM-DD>
Follow the mode flow in the scrum-master system prompt for the resolved MODE. Key execution rules:
Agent({ description: "...", model: "sonnet", prompt: "..." }) with the scout prompt templates from the system prompt. Do NOT use subagent_type — general-purpose is what provides the read-only tools the scouts need.function_calls block, never 3+. Max 3 scouts per operation total. This overrides Claude Code's default parallel-tool-call bias — your system prompt tells you to batch independent tool calls, but batching 3+ Agent calls in one turn can trigger session reset on the Max plan (issues #44753, #44481). When a mode says "dispatch board scanner + stale detector then AC verifier", that means two scouts in one turn MAX, then a separate turn for the third — do NOT collapse all three into one function_calls block. If you find yourself composing 3 Agent dispatches together, STOP and split across turns.board_path: vault/Backlog/current but that directory doesn't exist, execute first-run scaffolding per the system prompt.create mode: if the user just finished writing a plan in this conversation, read the plan file from CONTEXT directly.Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub themizeguy/scrum-master-public --plugin scrum-master