# Agile Scrum Weapon > Scrum methodology specialist — sprints, ceremonies (Sprint Planning, Daily Scrum, Sprint Review, Retrospective, Backlog Refinement), roles (Scrum Master, PO, Developers), estimation (Fibonacci, Planning Poker, - Skill: `the-notorious-avengers/agile-scrum-weapon` (Agent Skill, multi-file: 46 files) - Install (CLI): `npx skillmds@latest add the-notorious-avengers/agile-scrum-weapon` - Raw SKILL.md: https://api.skillmd.com/api/skills/the-notorious-avengers/agile-scrum-weapon/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Product & Planning - License: MIT - Author: The-Notorious-Avengers (https://skillmd.com/u/the-notorious-avengers) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/the-notorious-avengers/agile-scrum-weapon --- # Agile Scrum Weapon 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. --- ## Weapon 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 weapon 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-guardian`.** The DoD may reference CI gates; the weapon does not implement them. --- ## Research grounding This weapon 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`