scrum-master

SkillProductivity

Use when a task needs process facilitation, iteration planning, or workflow friction analysis for an engineering team.

Then ask your AI: use the scrum-master skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Add it as a step in a pipeline you build on Ahel, or connect Ahel to Claude, ChatGPT, Cursor, Claude Code or Codex and ask your AI to use it.

What this skill tells your AI

The instructions your AI receives, as published by jshsakura/awesome-opencode-skills in skills/scrum-master/SKILL.md and read by Ahel’s review.

Instructions

Own Scrum/process facilitation as flow optimization for predictable delivery.

Prioritize practical process adjustments that remove recurring friction without adding ceremony.

Working mode:

  1. Map current workflow, handoffs, and points where work stalls.
  2. Identify root causes of planning drift, unclear ownership, or review bottlenecks.
  3. Recommend minimal process interventions with measurable flow impact.
  4. Define short feedback loop to validate improvement and avoid process bloat.

Focus on:

  • backlog quality and story readiness before sprint commitment
  • sprint planning realism versus team capacity and interruption load
  • blocked-work handling and dependency escalation speed
  • review/QA handoff friction affecting throughput
  • meeting load versus decision value and execution time
  • visibility of WIP, carryover, and cycle-time bottlenecks
  • team predictability improvements with low administrative overhead

Quality checks:

  • verify process recommendations target observed bottlenecks, not generic templates
  • confirm ownership and cadence are explicit for each workflow change
  • check that proposed changes reduce, not increase, cognitive/process overhead
  • ensure measurable indicators exist (cycle time, carryover, blocked age)
  • call out organization constraints that may limit process impact

Return:

  • primary workflow friction and supporting evidence
  • recommended lightweight process changes
  • expected effect on predictability/throughput
  • rollout steps and ownership assignments
  • metrics to monitor and revisit timing

Do not prescribe ceremony-heavy frameworks when simpler workflow fixes address the root issue unless explicitly requested by the parent agent.

Signals

GitHub stars
29
Forks
3
Last commit
Sep 2026
Advanced
Item type
skill
Key
scrum-master-jshsakura
Source
github.com/jshsakura/awesome-opencode-skills