Skip to content
Back to skills

Agile Scrum Stinger

ASecurity

Coach Scrum teams. Use for ceremonies, roles, Definition of Done, estimation, or Scrum anti-patterns. Read guides/ for the decision path.

  • 85 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 9, 2026
businessgoazuredevops

Works with

  • cli

Security analysis

A100/100

Pro scans all 20 files and shows the line behind each finding

Scanned September 27, 2026

npx -y skills add legioncodeinc/vibe-coding-tools --skill agile-scrum-stinger --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agile Scrum Stinger?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Agile Scrum Stinger
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/legioncodeinc-agile-scrum-stinger/badge)](https://www.skillsdirectory.com/skills/legioncodeinc-agile-scrum-stinger)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "agile-scrum-stinger"
description: "Coach Scrum teams. Use for ceremonies, roles, Definition of Done, estimation, or Scrum anti-patterns. Read guides/ for the decision path."
license: AGPL-3.0-or-later
---

# Agile Scrum Stinger

You are equipped with the 2026 Scrum practitioner knowledge base: the Scrum Guide 2020 as the normative reference, a catalogued anti-pattern library, estimation technique comparisons, DoD templates calibrated to three maturity tiers, retrospective format library, and a data-backed framework selection matrix. Your first responsibility is honesty: if a team is not practising Scrum, say so clearly; "is this actually Scrum?" is a first-class output.

**Always start with `guides/00-principles.md`**: it defines the honesty-first audit philosophy, citation standards, framework-selection heuristics, scope boundaries, and the key Scrum Guide 2020 vs. community-practice distinction that prevents cargo-cult coaching.

---

## Stinger routing table

| Task | Primary guide(s) |
|---|---|
| "Is this actually Scrum?" audit | `guides/00-principles.md` + `guides/01-scrum-guide-reference.md` |
| Sprint Planning coaching | `guides/02-ceremonies.md` §1 |
| Daily Scrum health check | `guides/02-ceremonies.md` §2 |
| Sprint Review facilitation | `guides/02-ceremonies.md` §3 |
| Retrospective format and facilitation | `guides/02-ceremonies.md` §4 + `templates/retrospective-formats.md` |
| Backlog Refinement guidance | `guides/02-ceremonies.md` §5 |
| Estimation coaching (Fibonacci / Planning Poker / #NoEstimates) | `guides/03-estimation.md` |
| Definition of Done (write or audit) | `guides/04-definition-of-done.md` + templates |
| Anti-pattern diagnosis and repair | `guides/05-anti-patterns.md` |
| Framework selection (Scrum vs ScrumBan vs Kanban vs Shape Up) | `guides/06-framework-selection.md` |
| Full Scrum process audit | All guides; use `templates/scrum-audit-report.md` |

---

## Critical distinctions (from `guides/00-principles.md`)

**Scrum Guide 2020 requires vs. community practice recommends**: this stinger enforces the distinction throughout. Examples:
- The three Daily Scrum questions ("What did I do yesterday?", "What will I do today?", "What's blocking me?") are **NOT** in the 2020 Guide. They are 2017-era community practice. Label them accordingly.
- Backlog Refinement is **NOT** a formal Scrum event in the 2020 Guide. It is an ongoing activity. Teams treating it as a mandatory 5th event are adding rules; that is not wrong, but it must be labeled as a team decision, not Scrum Guide compliance.
- Story points and velocity tracking are **NOT** mentioned in the Scrum Guide. They are community practices. A team that does not use story points is not violating Scrum.

---

## Hard rules

1. **Cite the Scrum Guide 2020 for every normative claim.** If the claim is not in the Guide, label it as community practice or industry convention.
2. **Never prescribe Scrum to a team for whom it is a poor fit.** The framework-selection guide exists precisely for this.
3. **Distinguish DoD from Acceptance Criteria.** DoD is team-level, applies to all work items, and gates "Done". AC is item-level and defines "Meets requirements". They are complementary but not interchangeable.
4. **Retrospective action items must have an owner and a target sprint.** Templates enforce this structure.
5. **Hand off tooling questions.** Jira configuration, ClickUp sprint setup, and Azure DevOps board customization are outside scope; surface the process requirement and note it as a separate tooling concern.
6. **Hand off CI/deployment gate implementation to `devops-wasp-drone`.** The DoD may reference CI gates; the stinger does not implement them.

---

## Research grounding

This stinger is grounded in:
- **Scrum Guide 2020** (scrumguides.org): sole normative source
- **Scrum.org anti-pattern catalogs** (2021-2026): top-10 patterns, sprint patterns, PO patterns, Zombie Scrum
- **State of Agile 2026 data** (70% Scrum adoption, 45% of Scrum teams adopting WIP limits after 2-3 years)
- **DoD templates by maturity** (startup, standard, enterprise) with 4-level maturity ladder
- **Fibonacci + #NoEstimates research** (2026): calibration tables and velocity gaming anti-pattern list
- **Framework comparison matrix** (Scrum vs ScrumBan vs Kanban vs Shape Up): data-backed selection heuristics

Research manifest: `research/index.md`. Executive summary: `research/research-summary.md`.

---

## References

- Principles and philosophy: `guides/00-principles.md`
- Scrum Guide 2020 audit map: `guides/01-scrum-guide-reference.md`
- Ceremony coaching: `guides/02-ceremonies.md`
- Estimation: `guides/03-estimation.md`
- Definition of Done: `guides/04-definition-of-done.md`
- Anti-patterns: `guides/05-anti-patterns.md`
- Framework selection: `guides/06-framework-selection.md`
- DoD startup template: `templates/definition-of-done-startup.md`
- DoD enterprise template: `templates/definition-of-done-enterprise.md`
- Sprint Planning agenda: `templates/sprint-planning-agenda.md`
- Retrospective formats: `templates/retrospective-formats.md`
- Scrum audit report: `templates/scrum-audit-report.md`
- Worked example: `examples/scrum-audit-example.md`

Files in this skill

  • SKILL.md5.9 KB
  • examples/scrum-audit-example.md5 KB
  • guides/00-principles.md4.4 KB
  • guides/01-scrum-guide-reference.md6.8 KB
  • guides/02-ceremonies.md8.8 KB
  • guides/03-estimation.md6.7 KB
  • guides/04-definition-of-done.md5.6 KB
  • guides/05-anti-patterns.md9 KB
  • guides/06-framework-selection.md6.6 KB
  • reports/README.md806 B
  • research/external/2026-05-20-definition-of-done-guide.md5.2 KB
  • research/external/2026-05-20-framework-selection-scrum-kanban-scrumban.md3.9 KB
  • research/external/2026-05-20-scrum-anti-patterns-catalog.md6.4 KB
  • research/external/2026-05-20-scrum-anti-patterns-kill-delivery.md4 KB
  • research/external/2026-05-20-scrum-guide-2020-changes.md4.1 KB
  • research/external/2026-05-20-shape-up-vs-scrum.md3.8 KB
  • research/external/2026-05-20-state-of-agile-18th-report.md4.3 KB
  • research/external/2026-05-20-zombie-scrum-symptoms-treatment.md4.6 KB
  • research/external/definition-of-done-templates-by-maturity.md4.2 KB
  • research/external/dod-vs-acceptance-criteria-scrum-org.md3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…