agile-scrum-stinger

Audits Scrum processes against the Scrum Guide 2020 and coaches ceremonies, estimation, and Definition of Done.

84|37|Updated May 23, 2026
One-click install
npx skills add https://github.com/legioncodeinc/vibe-coding-tools --skill agile-scrum-stinger-legioncodeinc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agile-scrum-stinger
Source: https://github.com/legioncodeinc/vibe-coding-tools/tree/main/src/skills/agile-scrum-stinger
Command: npx skills add https://github.com/legioncodeinc/vibe-coding-tools --skill agile-scrum-stinger-legioncodeinc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often believe they are practising Scrum when they are actually running a degraded subset: missing Sprint Goals, skipped Retrospectives, proxy Product Owners, and gamed velocity metrics. This Skill provides an honesty-first audit and coaching knowledge base grounded in the Scrum Guide 2020, so teams get a clear verdict on whether their process is actually Scrum and concrete repair moves when it is not. ## Core Features & Use Cases - Scrum Guide 2020 audit: Checklists for roles, events, artefacts, and commitments that distinguish normative Guide requirements from community practices (e.g., the three Daily Scrum questions are not in the 2020 Guide). - Ceremony and estimation coaching: Per-ceremony failure modes and repair moves for Sprint Planning, Daily Scrum, Sprint Review, Retrospective, and Backlog Refinement, plus Fibonacci, Planning Poker, T-shirt sizing, and #NoEstimates guidance. - Anti-pattern catalog and framework selection: Named diagnoses (Zombie Scrum, HiPPO PO, PO by Proxy, velocity gaming) with repair moves, and a scored decision matrix for Scrum vs ScrumBan vs Kanban vs Shape Up. - Use Case: A 6-person SaaS team asks "should we switch to Kanban?" The Skill audits their process, identifies Scrum-but with no Sprint Goal and stopped Retrospectives, scores the framework matrix, and recommends fixing Scrum with a written DoD and restarted retros instead of migrating frameworks. ## Quick Start Ask the assistant to audit our Scrum process and tell us whether what we are doing is actually Scrum.

Frequently Asked Questions about agile-scrum-stinger

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

FAQPage Schema
How do I audit whether my team is actually doing Scrum?▼

Run the audit checklists mapped to the Scrum Guide 2020 covering roles, events, artefacts, and commitments. The output is a verdict of either Scrum with improvement areas or Scrum-but with named deviations and repair moves.

What is the difference between Definition of Done and Acceptance Criteria?▼

Definition of Done is team-level and gates whether any Increment counts as Done, while Acceptance Criteria are item-level and define whether one story meets requirements. A story passing its AC but failing the DoD is not Done.

When should a team switch from Scrum to Kanban or ScrumBan?▼

Consider ScrumBan when more than 30% of Sprint work is unplanned for three consecutive Sprints, and Kanban when work is primarily support or interrupt-driven. The decision matrix scores predictability, commitment comfort, unplanned work, stakeholder cadence, and team experience.

Are the three Daily Scrum questions required by Scrum?▼

No. The Scrum Guide 2020 removed the prescribed three questions from the 2017 version; the format is decided by the Developers. Teams using the three questions are following community practice, not a Scrum requirement.

Why do our retrospectives keep producing the same issues every sprint?▼

Retrospectives fail when they end without action items that have a single owner and a target sprint. Review previous action items as the first agenda item and consider anonymous formats if psychological safety is low.

Does this Skill configure Jira or ClickUp sprint boards?▼

No. Project management tooling configuration is explicitly out of scope; the Skill surfaces the process requirement and notes it as a separate tooling concern. CI/CD pipeline gates referenced in a DoD are handed off to a DevOps specialist.