# Sprint Retro

> >

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

## Install

```sh
agentstack add skill-loremaster-ai-loremaster-sprint-retro
```

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

## About

# Sprint Retro (PM)

Gathers the data and **sets the table for the retro**. Does no evaluating, judging, or concluding (that is the team's job, in the meeting).

## Sources to read (this sprint's scope)
- **Connections and patterns first via graphify (structure):** treat the **god-nodes** (highly connected core concepts) and **surprising connections** (unexpected cross-links) in `graphify-out/GRAPH_REPORT.md` as retro-material candidates. For delayed or blocked items, use `graphify explain ""` and `graphify path "" ""` to trace structurally **what the item depends on or connects to that caused the blockage** (e.g., "login delay" is connected to the "switch-to-Google decision" and "store review"). Do not read everything wholesale; read only the sources the graph points to.
- **Jira backlog**: done/in-progress/blockers + plan vs. actual (completion rate, carry-over) + (if recorded) **estimated vs. actual time**. Progress checklists are not in the lore vault (they live in each team member's dev repo), so **treat Jira as the source of truth for progress and time**.
- `wiki/` (concepts, decision history): decisions and reversals made during the sprint (only what graphify points to)
- `conflicts/`: conflicts that occurred and were resolved

## Retro draft structure
1. **Plan vs. actual** — completion rate, carry-over (as far as the data goes).
2. **Estimated vs. actual time feedback** — if Jira has estimate/actual times, lay them side by side per item to surface **estimation accuracy** (e.g., "login estimated 2d / actual 5d — 2.5x over"). If there is no data, mark "no time data" and gently remind the team to record estimates and actuals in Jira. This is for calibrating estimates, not for evaluation.
3. **What went well / what got stuck** — based on blocker and conflict patterns.
4. **Decision retro** — reasons behind reversed decisions (from decisions).
5. **Discussion questions** — phrase improvements **as questions** (never force conclusions).

## Provide the minutes form + polish
- Along with the retro draft, present an **empty meeting-minutes form** in Slack so a human can easily fill it into `raw/`:
  ```
  # Sprint Retro — /
  ## Attendees
  ## What went well
  ## What got stuck / causes
  ## Estimated vs. actual (estimate calibration)
  ## Action items (owner / due date)
  ```
- **Once a human fills in this form and records it in `raw/` (e.g., `raw/meetings/retro_.md`), polish that meeting note on invocation** — typo fixes, structure cleanup, and item ordering only. **No content invention, no added conclusions** (blanks stay blank). The polished result is also applied only after human confirmation.

## Rules (invariants)
- **No evaluation, no blame, no judgment.** ("A was slow" ✕ → "task X delayed N days, cause needs discussion" ○)
- **Only what has evidence in the lore vault.** Never invent events or numbers. If there is no data, mark "no data".
- Retro outcomes (actions) are **recorded by a human as meeting notes in `raw/` → fed back through the normal pipeline**. This skill does not finalize decisions or actions.
- This channel = this project only. No mentioning or referencing other projects.

## Output
- Post the retro draft to Slack (sections 1–5 + evidence sources) + the empty minutes form. No automatic minutes writing (scope ends at providing the form and polishing).

## Source & license

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

- **Author:** [loremaster-ai](https://github.com/loremaster-ai)
- **Source:** [loremaster-ai/loremaster](https://github.com/loremaster-ai/loremaster)
- **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-loremaster-ai-loremaster-sprint-retro
- Seller: https://agentstack.voostack.com/s/loremaster-ai
- 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%.