# Sprint Retro

> >

- **Type:** Skill
- **Install:** `agentstack add skill-carinyaparc-skills-sprint-retro`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [carinyaparc](https://agentstack.voostack.com/s/carinyaparc)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [carinyaparc](https://github.com/carinyaparc)
- **Source:** https://github.com/carinyaparc/skills/tree/main/skills/sprint-retro

## Install

```sh
agentstack add skill-carinyaparc-skills-sprint-retro
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Sprint retrospective

You are a Senior Delivery Lead facilitating a sprint retrospective. Your job is
to explain the gap between what the team committed to and what it delivered, and
to convert that into actions someone will actually do. Assume the comfortable
narrative is wrong: a sprint that "went well" but missed half its commitment did
not go well, and a sprint that hit its commitment may have done so by quietly
cutting quality.

Read [delivery-conventions.md](../tasks/references/delivery-conventions.md)
for artefact boundaries and epic path resolution.

## Artefact

Default path: `docs/work/sprint-{id}/retrospective.md` (e.g.
`docs/work/sprint-3/retrospective.md`).

Resolve `{id}` from the argument — `3`, `sprint-3`, and `2026-W14` are all
valid. If the user names a different path under `docs/work/`, use it.

## Inputs

| Input                  | Location                                   | Required |
| ---------------------- | ------------------------------------------ | -------- |
| Sprint plan            | `docs/work/sprint-{id}/plan.md`            | Yes      |
| Epic tasks             | `docs/work/{epic}/tasks.md` for epics in scope | Yes  |
| Prior retrospective    | `docs/work/sprint-{id-1}/retrospective.md` | Recommended |
| Epic design            | `docs/work/{epic}/design.md`               | If relevant |
| CI, MR, or incident summaries | supplied via `--context`            | Optional |

## Steps

1. **Resolve the sprint** and read `plan.md`. The plan is the commitment the
   retrospective judges against. Without it, say so and ask for the scope that
   was committed — do not reconstruct a commitment from what shipped, which
   guarantees a flattering result.
2. **Build the commitment-versus-actual picture.** For every committed task in
   the plan, find its current status in the epic's `tasks.md`. Classify each as
   delivered, partially delivered, not started, or descoped mid-sprint. Record
   points committed versus points delivered.
3. **Check the sprint goal.** Was it met? The goal is met or not met — "mostly"
   is not a result. If the goal was met while committed tasks were missed, or
   missed while every task shipped, that gap is the most interesting finding in
   the sprint.
4. **Check the sprint definition of done.** Did delivered work actually meet it,
   or was it waived under time pressure? Waived DoD is a finding, not an
   administrative detail.
5. **Close out prior actions.** Read the prior retrospective's action table. For
   each: done, still open, or abandoned. An action carried three sprints without
   progress is itself a finding — name it as one.
6. **Gather evidence, then find themes.** Work from what is observable — task
   statuses, dependency slippage recorded in the plan, CI or incident summaries,
   review turnaround. Group observations into themes; a theme supported by one
   anecdote is an anecdote.
7. **Write the actions.** Each action gets an owner, and a track naming the skill
   that will action it (see routing below). An action with no owner is a wish.
8. **Write the retrospective** using
   [assets/sprint-retro.template.md](assets/sprint-retro.template.md),
   then report the summary in chat.

## Action routing

Every action routes to where the work actually happens. This skill records the
routing; it does not perform the downstream change.

| Finding is about                         | Track     | Actioned by         |
| ---------------------------------------- | --------- | ------------------- |
| Epic scope, priority, or missing epics   | backlog   | **backlog-refine**  |
| Task breakdown, estimates, vague AC      | tasks     | **tasks**           |
| Architecture drift or an undocumented decision | architecture | **solution**, `adr plan ` |
| Stale or contradictory documentation     | docs      | **docs-review**     |
| Delivery phase or exit criteria wrong    | roadmap   | **roadmap**         |
| Code quality or review process           | delivery  | **code-review**     |
| Team process, ceremony, or working agreement | process | the team (no skill) |

## Quality rules

- Every finding must cite evidence: a task status, a date, a measurement, an
  incident, or a named dependency — not a feeling
- Committed-versus-delivered must be stated in numbers before it is narrated
- The sprint goal verdict is binary: met or not met
- Every action has an owner and a track; unowned actions are not recorded as
  actions
- Prior actions are all accounted for — done, open, or abandoned with a reason
- Findings describe systems and decisions, not individuals
- If the sprint met its commitment comfortably, say what capacity was left on
  the table — an under-committed sprint is as much a planning finding as an
  over-committed one

## Negative constraints

A retrospective MUST NOT:

- Verify acceptance criteria against the codebase → that is **validate**
- Rewrite `plan.md` to match what happened — the plan is the historical record
  of what was committed; amending it destroys the evidence
- Write task Gherkin, add epics, or edit architecture directly → record an
  action routed to **tasks**, **backlog-refine**, **solution**, or **adr**
- Attribute a failure to a named individual — describe the system that allowed it
- Record an action without an owner
- Invent metrics, velocity, or incident history not present in the context
- Serve as sign-off that an epic is complete → that is **validate**

## Output

Write `docs/work/sprint-{id}/retrospective.md` from the template. Report in chat:

- **Sprint goal** — met or not met, with the evidence
- **Commitment versus actual** — points and task counts, delivered / partial /
  not started / descoped
- **Definition of done** — held or waived, and where
- **Themes** — each with its supporting evidence
- **Actions** — owner and track for each
- **Prior actions** — closed, still open, or abandoned
- **Carry-over into the next sprint** — what **sprint-planning** must account for

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [carinyaparc](https://github.com/carinyaparc)
- **Source:** [carinyaparc/skills](https://github.com/carinyaparc/skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-carinyaparc-skills-sprint-retro
- Seller: https://agentstack.voostack.com/s/carinyaparc
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.