retro

retro is a skill for Claude Code from VandanaAjayDubey111/great-pm. It costs 52 tokens per session (2,799 once invoked), scanned A, original, MIT.

A structured sprint-retrospective guide for reviewing what went well, what went poorly, and what the team should change. A retrospective is a meeting held after a sprint to learn from the work.

In plain words
What is it for?
Use it to run a retrospective, organize feedback, and create action items with owners and deadlines.
Why use it?
It turns general team feedback into specific actions instead of leaving lessons and problems unresolved.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions Codex.

Part of the great-pm plugin — 114 skills, 34 commands, 48 agents, 5 hooks shipped together

Good fit Use it to run a retrospective, organize feedback, and create action items with owners and deadlines.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vandanaajaydubey111/great-pm/retro
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 VandanaAjayDubey111/great-pm --skill retro
Clone the repo
git clone --depth 1 https://github.com/VandanaAjayDubey111/great-pm

Made for: Claude Code.

Or install great-pm, the plugin that ships this one along with the rest of its 114 skills, 34 commands, 48 agents, 5 hooks.

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.

agentmods badge for retro

README.md
[![agentmods](https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/retro/github.svg)](https://agentmods.dev/skills/vandanaajaydubey111/great-pm/retro)
Your own site
<a href="https://agentmods.dev/skills/vandanaajaydubey111/great-pm/retro"><img src="https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/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.

agentmods 80×15 button for retro

Your own site · 80×15
<a href="https://agentmods.dev/skills/vandanaajaydubey111/great-pm/retro"><img src="https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/retro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,799 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00052 $0.02799
Opus 5.5 $0.00021 $0.01120
Sonnet 5.5 $0.00010 $0.00560
Haiku 4.5 $0.00005 $0.00280

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

Security

Grade A, and why

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 1mo 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.

plugins/great-pm/skills/retro/SKILL.md · 187 lines

How it starts

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

Codex host binding

  • Treat references to Claude slash workflows as the equivalently named Codex skill.
  • Before delegating to any specialist, read the great-pm-runtime skill and the selected packaged role file.
  • Treat "invoke", "assign", "delegate", "spawn", and source Agent-tool instructions as a required Codex spawn_agent call with that role and a bounded assignment.
  • For the spawn tool's task_name or agent_name identifier, replace canonical role-name hyphens with underscores (query-refiner-pm → query_refiner_pm). Keep canonical names unchanged in prompts, filenames, verdict logs, and user-facing output; this is an internal identifier mapping, not a role rename.
  • Store every returned agent identifier. Never call a wait tool until a spawn has returned an identifier, and wait only on identifiers returned by successful spawns.
  • If spawn_agent is unavailable or a spawn fails, report BLOCKED; do not impersonate the specialist or wait on an empty agent set.
  • Resolve bundled paths from the installed GreatPM plugin root.
  • Ignore Claude-only model aliases, colors, turn limits, and tool allowlists.
  • Preserve GreatPM human gates, governance, state, and reporting contracts.

Provenance. Vendored from phuryn/pm-skills@retro (MIT, Paweł Huryn / Product Compass — github.com/phuryn/pm-skills). Adapted into great-pm 2026-05-29 with attribution. Host agent: pm-lead.

Sprint Retrospective Facilitator

Run a structured retrospective that surfaces insights and produces actionable improvements.

Context

You are facilitating a retrospective for $ARGUMENTS.

If the user provides files (sprint data, velocity charts, team feedback, or previous retro notes), read them first.

Instructions

  1. Choose a retro format based on context (or let the user pick):

    Format A — Start / Stop / Continue:

    • Start: What should we begin doing?
    • Stop: What should we stop doing?
    • Continue: What's working well that we should keep?

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

  1. 1mo ago First seen · 187 lines · 52 tokens per session scan A 655346ed7378

Subscribe to this mod's changes

retro is a skill published in the GitHub repository VandanaAjayDubey111/great-pm (3 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 2,799 once invoked, about $0.0002 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-09-21.

Related

Other skills, from other repositories

caixun-work-hours

A work-hours reporting assistant for RichPMS, a project time-tracking system. It turns conversation details, code records, or your description into a daily report, lets you confirm it, and then saves or submits it.

nexus-research-lab/nexus · 77 tokens

commonly

You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…

Team-Commonly/commonly · 0 tokens

nexus-configuration

A skill for reading, planning, approving, and checking configuration in Nexus, the current private conversation or room. It covers settings such as agents, rooms, providers, channels, connectors, skills, models, tools, and MCP connections.

nexus-research-lab/nexus · 45 tokens

sherpa

Guiding workflows by decomposing complex tasks (Epics) into Atomic Steps under 15 minutes each, with progress tracking and drift prevention. Use when complex decomposition is needed.

simota/agent-skills · 39 tokens

tome

Converting technical knowledge into durable learning documents and publishable articles. Use for diff-based teaching, decision records, onboarding, note/Zenn/Qiita/dev.to posts, article series, retrospectives, and cross-platform repurposing.

simota/agent-skills · 50 tokens

pm-planning

Decomposition methodology for pm agent — turns an approved ARCH document into a Beads task list with explicit dependencies, time-boxes, and acceptance criteria. The pipeline can only orchestrate work it can see; this skill defines what "seeable work" looks like.

avelikiy/great_cto · 57 tokens