skills.rest
jshsakura
jshsakuraCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

scrum-master

Diagnose Scrum delivery frictions across sprint planning, reviews, and standups.

22|2|Updated Mar 24, 2026
Search Tags:#workflow#planning#agile#throughput#scrum#facilitation#cycle-time
One-click install
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill scrum-master-jshsakura
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scrum-master
Source: https://github.com/jshsakura/awesome-opencode-skills/tree/main/skills/scrum-master
Command: npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill scrum-master-jshsakura

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agile teams often struggle with unclear workflows, repeated handoffs, and drift in sprint planning that reduce predictability and flow.

Core Features & Use Cases

  • Map current sprint workflows and handoffs to identify bottlenecks.
  • Recommend lightweight process changes with measurable impact on cycle time and throughput.
  • Align ownership, cadence, and review handoffs to improve delivery flow.

Quick Start

Map the current sprint workflow and propose a minimal, measurable improvement.

Frequently Asked Questions about scrum-master

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify bottlenecks in my sprint workflow?▼

To identify sprint workflow bottlenecks, map current handoffs and process frictions across your team. This helps pinpoint repeated handoffs and unclear workflows that reduce delivery predictability and flow.

What is the best way to reduce cycle time and improve throughput in agile delivery?▼

The best way to reduce cycle time and improve throughput is aligning ownership, cadence, and review handoffs. Recommend lightweight process changes to directly impact measurable flow metrics like WIP.

How do I fix drift and unclear workflows in sprint planning?▼

Fix sprint planning drift by diagnosing frictions in Scrum-based delivery. Map the current sprint workflow to propose minimal, measurable improvements that restore predictability and alignment.

Does this approach work for daily standups and sprint reviews?▼

Yes, this approach works for daily standups and sprint reviews by diagnosing ongoing workflow bottlenecks. It applies lightweight guardrails and cadence adjustments across iteration planning and reviews.

When should I not use lightweight process changes for agile delivery?▼

Avoid lightweight process changes when your team lacks measurable flow metrics like cycle time and throughput. Without baseline WIP data, diagnosing Scrum delivery frictions and validating improvements is difficult.

Related Skills

Explore More Software Engineering Skills→
markus41markus41
1

kanban

Configure Kanban boards with WIP limits and compute flow metrics.

Community
Basic
qa-amanqa-aman
19

flow-metrics-review

Analyze cycle time, WIP, lead time, and throughput to identify delivery bottlenecks.

Community
Advanced
coreyhulencoreyhulen

github-project-management

Automate GitHub issue tracking, project board synchronization, and sprint planning.

Community
Advanced
Lobbi-DocsLobbi-Docs
18

kanban

Configure Kanban boards with WIP limits and analyze flow metrics.

Official
Basic