What is audit-sprint-retrospective-ado?

An audit tool for team retrospectives recorded in Azure DevOps, Microsoft's platform for managing software projects. A retrospective is a meeting where a team reviews what went well, what went poorly, and what to improve.

Use it to review retrospective data from an Azure DevOps board, wiki page, or tagged work items, then produce findings and follow-up actions.

It turns scattered retrospective notes into a structured summary and checks whether agreed actions have owners and are tracked as work items. It also identifies repeated themes across the team's feedback.

audit-sprint-retrospective-ado — Skill by abrahamFerga/scrum-skills

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add abrahamFerga/scrum-skills --skill audit-sprint-retrospective-ado

Clone the repo

git clone --depth 1 https://github.com/abrahamFerga/scrum-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/audit-sprint-retrospective-ado/github.svg)](https://agentmods.dev/skills/abrahamferga/scrum-skills/audit-sprint-retrospective-ado)

Your own site

<a href="https://agentmods.dev/skills/abrahamferga/scrum-skills/audit-sprint-retrospective-ado"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/audit-sprint-retrospective-ado/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/abrahamferga/scrum-skills/audit-sprint-retrospective-ado"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/audit-sprint-retrospective-ado.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 145 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,230 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00145	$0.02230
Opus 5.5	$0.00058	$0.00892
Sonnet 5.5	$0.00029	$0.00446
Haiku 4.5	$0.00015	$0.00223

Measured 2mo ago against content hash 831ed26d2f79, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

audit-sprint-retrospective-ado scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/audit-sprint-retrospective-ado/SKILL.md · 192 lines

How it starts

The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ADO Retrospective Audit

Purpose

A retrospective that produces no followed-through action items is just venting. This skill reads the retro data from ADO, turns it into a clear structured summary, checks that every action item is properly captured and owned, and surfaces patterns the team can act on — so the Retrospective actually improves the way the team works.

Prerequisites

Requires an active Azure DevOps MCP connection. If mcp__azure-devops__* or mcp__ado__* tools are not available, stop and inform the user.

Step 1 — Locate the retrospective data

Teams store retrospectives in ADO in different places. Ask:

"Where does your team record retrospectives — the ADO Retrospectives board extension, a wiki page, or work items tagged as retro action items? Or should I search all three?"

Then retrieve accordingly:

ADO Retrospectives extension board The extension stores retro content as work items under a hidden area. Search for them using wit_query_by_wiql or search_workitem with terms like "retrospective", the sprint name, or the board name. Look for items with types or tags like Retrospective, FeedbackItem, or ActionItem.

Wiki Use wiki_list_pages to find pages named after the sprint or containing "retrospective", "retro", or "sprint review". Then use wiki_get_page_content to retrieve the full content.

Work items (retro-tagged) Use search_workitem or wit_query_by_wiql to find items tagged retrospective, retro-action, or similar. Also search for items whose title contains "action item from retro" or whose description links to a retrospective.

If all three return nothing: ask the user to paste the retro content directly or share a link to the wiki page.

Store everything found as $RETRO_DATA. Note the source(s) for the summary.

Step 2 — Parse and structure the content

Extract and categorise all content from $RETRO_DATA into the standard retrospective buckets. Adapt to whatever format the team used:

Read the full file on GitHub · 192 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 192 lines · 145 tokens per session scan A 831ed26d2f79

Subscribe to this mod's changes

audit-sprint-retrospective-ado is a skill published in the GitHub repository abrahamFerga/scrum-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 145 tokens to every session and 2,230 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Analytics and metrics Project management agent-skills agents agile ai awesome claude

audit-sprint-retrospective-ado next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
audit-sprint-retrospective-adoabrahamFerga/scrum-skills	Skill	5	6mo ago	MIT	A	145	Claude Code, Codex
xquikashish7802/awesome-api-skills	Skill	13	3d ago	MIT	A	0	Claude Code, Codex
argo-cdashish7802/awesome-api-skills	Skill	13	3d ago	MIT	A	0	Claude Code, Codex
azure-openaiashish7802/awesome-api-skills	Skill	13	3d ago	MIT	A	0	Claude Code, Codex
biomeashish7802/awesome-api-skills	Skill	13	3d ago	MIT	A	0	Claude Code, Codex
bullmqashish7802/awesome-api-skills	Skill	13	3d ago	MIT	A	0	Claude Code, Codex
clerkashish7802/awesome-api-skills	Skill	13	3d ago	MIT	A	0	Claude Code, Codex