Agile Scrum Stinger logo

Agile Scrum Stinger

Organization
legioncodeinc
agile-scrum-stinger

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

Overview

Publisherlegioncodeinc
Repositoryvibe-coding-tools
Skill nameagile-scrum-stinger
Stars
94
Forks
44
Bundled files
14
LicenseAGPL-3.0-or-later
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 14 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by legioncodeinc on GitHub. Read the source before you install it.

Installation

Install the Agile Scrum Stinger AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/legioncodeinc/vibe-coding-tools/tree/main/plugins/business-and-product-tools/skills/agile-scrum-stinger
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/legioncodeinc/vibe-coding-tools.git /tmp/vibe-coding-tools
mkdir -p .claude/skills
cp -r /tmp/vibe-coding-tools/plugins/business-and-product-tools/skills/agile-scrum-stinger .claude/skills/agile-scrum-stinger
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Agile Scrum Stinger in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Agile Scrum Stinger on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Agile Scrum Stinger is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

TaskPrimary guide(s)
"Is this actually Scrum?" auditguides/00-principles.md + guides/01-scrum-guide-reference.md
Sprint Planning coachingguides/02-ceremonies.md §1
Daily Scrum health checkguides/02-ceremonies.md §2
Sprint Review facilitationguides/02-ceremonies.md §3
Retrospective format and facilitationguides/02-ceremonies.md §4 + templates/retrospective-formats.md
Backlog Refinement guidanceguides/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 repairguides/05-anti-patterns.md
Framework selection (Scrum vs ScrumBan vs Kanban vs Shape Up)guides/06-framework-selection.md
Full Scrum process auditAll 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

Executive summary: the shipped research/research-summary.md. The research manifest, research/index.md, is source-repository research, not shipped with the plugin.


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

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Agile Scrum Stinger AI skill do?

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

Why use Agile Scrum Stinger on TypingMind?

Because you install it once and use it with any model. Agile Scrum Stinger is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Agile Scrum Stinger in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/legioncodeinc/vibe-coding-tools/tree/main/plugins/business-and-product-tools/skills/agile-scrum-stinger. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Agile Scrum Stinger?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Agile Scrum Stinger?

As many as you like. As long as a model supports skills, you can use Agile Scrum Stinger with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Agile Scrum Stinger AI skill free?

Yes. It is published on GitHub by legioncodeinc under the AGPL-3.0-or-later license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇