A guided end-of-iteration review for an agilemarkdown project. An iteration is a short period of planned work; the review asks what worked, what did not, and what the team should change.

Use it at the end of an iteration to review delivered stories, velocity, cycle time, rejection rate, work types, learnings, and team agreements.

Teams can repeat the same problems when they do not examine completed work and its measurements. This process combines project data with team notes to support concrete improvements.

How mreider/agilemarkdown configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to mreider/agilemarkdown. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/mreider/agilemarkdown/master/.claude/skills/am-retro/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/mreider/agilemarkdown

Made for: Claude Code.

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/mreider/agilemarkdown/am-retro/github.svg)](https://agentmods.dev/skills/mreider/agilemarkdown/am-retro)

Your own site

<a href="https://agentmods.dev/skills/mreider/agilemarkdown/am-retro"><img src="https://agentmods.dev/badge/skills/mreider/agilemarkdown/am-retro/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/mreider/agilemarkdown/am-retro"><img src="https://agentmods.dev/badge/skills/mreider/agilemarkdown/am-retro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 817 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.00065	$0.00817
Opus 5	$0.00032	$0.00409
Sonnet 5	$0.00013	$0.00163
Haiku 4.5	$0.00006	$0.00082

Measured 10d ago against content hash 0c8773b8fd72, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

am-retro 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 10d 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.

.claude/skills/am-retro/SKILL.md · 95 lines

How it starts

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

am-retro

A retro is a moment to ask three questions: what worked, what didn't, what changes do we make. Pivotal teams ran them at the iteration boundary. This skill walks the human through one, using the data already in the repo.

When this fires

Iteration boundary (the last accepted story for the iteration just landed, or the human says "wrap up").
Human asks for a retro.
User invokes /am-retro.

What to do

Pull the iteration's data via MCP tools:
- dashboard() for velocity, volatility, cycle time median, latest rejection rate.
- velocity_history(backlog=<name>) for recent iteration deltas.
- type_mix() for feature/bug/chore split.
- Read learnings.md if present (via the file system; it is not a story file, so no MCP wrapper).
- Read team-agreements.md if present.

Render a one-screen summary in this shape:

Iteration X retro

Numbers:
  velocity:       <n> pts (was <prev>)
  volatility:     <n>%
  cycle time:     <n>d (median)
  rejection rate: <n>% (target band 5-15%)
  type mix:       feature <n>%, bug <n>%, chore <n>%

What landed:
  - <story> (<type>, <pts>)
  ...

What got rejected (if any):
  - <story>, <reason>
  ...

Carryover:
  <items still in started/finished/delivered that did not accept>

Ask the human three questions, one at a time, waiting between each:
- What worked? Give them a moment. Then offer to record their answer to learnings.md via the record_learning tool.
- What did not work? Same shape. The signal here is the one that informs the next agreement or canon-tightening.
- What changes for next iteration? This is where new working agreements come from. If the human names a behavior, a moment, and a default, propose adding it to team-agreements.md via the team_agreements tool with set: and the appended line.
If rejection rate is outside the 5-15% target band, surface that separately. Below 5% means the PM is not being careful enough; above 15% means the team is shipping work the PM does not want. Ask the human what they think is driving it.

Read the full file on GitHub · 95 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.

10d ago First seen · 95 lines · 65 tokens per session scan A 0c8773b8fd72

Subscribe to this mod's changes

am-retro is a skill published in the GitHub repository mreider/agilemarkdown (7 stars, last pushed 3mo ago), licensed MIT. It adds 65 tokens to every session and 817 once invoked, about $0.0003 per session on Opus 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.

Project management agile markdown product-management scrum

gr-product-dev-ops

🇺🇸 Your dev team ships features nobody asked for while user-reported bugs pile up for months. Operations blames engineering for ignoring users; engineering blames operations for not understanding technical constraints. This gives you the complete Product × Engineering × Operations alignment SOP — from unified…

Gingiris-1031/gingiris-skills · 576 tokens

scrumboy-board-operator

Operate Scrumboy projects and boards through MCP or Agoragentic APIs. Use when an agent needs to inspect board state, plan sprint work, create todos, move cards, manage tags, or summarize project health.

markrai/scrumboy · 51 tokens

pm-skills

Use when coordinating project-delivery work across the 8 project-management sub-skills — sprint/velocity analytics, portfolio health, Jira/JQL, Confluence, Atlassian admin, templates, meeting analysis, team comms. Triggers on 'our sprints feel off', 'project health report', 'audit our Jira permissions', 'when will it…

mrDesign-ww/vault-os · 179 tokens

project-manager

This skill has been upgraded with agentic AI capabilities, OKR/KPI integration patterns, and async-first workflows based on 2026 PM best practices research.

buiphucminhtam/forgewright · 68 tokens

sprint-planning

Sprint & Release Planning: Helps with sprint planning, backlog grooming, story estimation, release planning, and roadmap creation. Use this skill whenever the user wants to plan a sprint, groom the backlog, write user stories, estimate tasks, plan a release, create a roadmap, prioritize features, or structure a…

camilooscargbaptista/cto-toolkit · 124 tokens

dangerous-animals-of-pm-generator

Generate creature acronyms that name PM dysfunctions, blockers, or winning strategies. Use when you want to give your team shared vocabulary for the animals hiding in your product work.

deanpeters/product-manager-prompts · 44 tokens

agilemarkdown: Skill for Claude Code