What is retrospective?

A structured review of a completed sprint or milestone, based on the work, progress, blockers, bugs, and earlier retrospectives. A retrospective is a team review of what happened and what should change next time.

Use it at the end of a sprint, when a milestone closes, after a missed deadline, or when repeated problems appear. It drafts a retrospective document for the team to confirm.

It turns delivery data into practical improvements instead of relying on memory or opinions alone. It can reveal recurring blockers, missed deadlines, and patterns across iterations.

retrospective — Skill for Claude Code by cenconq25

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 cenconq25/claude-code-app-studio --skill retrospective

Clone the repo

git clone --depth 1 https://github.com/cenconq25/claude-code-app-studio

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/cenconq25/claude-code-app-studio/retrospective/github.svg)](https://agentmods.dev/skills/cenconq25/claude-code-app-studio/retrospective)

Your own site

<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/retrospective"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/retrospective/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/cenconq25/claude-code-app-studio/retrospective"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/retrospective.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,793 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.00046	$0.01793
Opus 5	$0.00023	$0.00897
Sonnet 5	$0.00009	$0.00359
Haiku 4.5	$0.00005	$0.00179

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

Security

Grade A, and why

retrospective 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 5d 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/retrospective/SKILL.md · 254 lines

How it starts

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

Retrospective

A structured retro pulls signal from data the team already produced — sprint plan, story files, mid-sprint updates, bug counts — and turns it into actionable practice changes. This skill drafts the retro; the team confirms.

Output: production/retros/sprint-<NNN>-retro.md or production/retros/milestone-<name>-retro.md

Purpose / When to Run

Run when:

A sprint just ended
A milestone closed (regardless of outcome)
A deadline was missed and the team wants to learn from it
A recurring pattern of failures shows up

Inputs

The sprint plan or milestone doc
All stories in scope
Any ## Mid-Sprint Update sections
production/qa/bugs/ if present
Previous retros (for continuity)

Outputs

A retro doc at production/retros/<scope>-retro.md

Phase 1: Resolve Scope

If argument names a sprint or milestone, read it directly.

If empty, ask:

Prompt: "Retro on what?"
Options: Last sprint, Specific sprint (free text), Last milestone, Specific milestone (free text)

For "Last sprint", glob production/sprints/*.md and pick the most recent.

Phase 2: Gather Data

Read:

The sprint plan or milestone doc — extract original goal, original scope, capacity
All stories in scope — current Status, time-stamps, any in-story notes
Mid-Sprint Update sections — additions, removals, reasons
Bugs filed during the period (if present)
Last retro (continuity check — were prior commitments met?)
Concept doc Primary Metric — did the work move it?

Compute:

Planned stories vs. completed
Velocity (story-days)
Carry-out
Blocker count and total blocker duration
Bug count by severity created during the period
Bugs closed during the period

Phase 3: Surface Patterns

Cross-reference data for patterns:

Estimation accuracy

Compare estimates (if /estimate was run) to actual time
Flag stories that took >2x estimate as estimation outliers — useful signal

Drag sources

Stories Blocked >2 days — what blocked them?
Common blocker categories: missing ADR, missing UX, missing backend, third-party SDK, store / device issues
Group by category — the most-frequent blocker is the highest-leverage retro target

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

5d ago First seen · 254 lines · 46 tokens per session scan A 82e0e8c70d60

Subscribe to this mod's changes

retrospective is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 1,793 once invoked, about $0.0002 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-09-03.

Project management

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens