Run any Skill in Manus with one click

Get Started

retro

Stars5

Forks0

UpdatedMarch 28, 2026 at 06:44

Run a retrospective for the last completed work item. Pulls DORA metrics, summarizes flow, captures keep/stop/start.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

RD-DCS

RD-DCS/venutian-antfarm

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	retro
description	Run a retrospective for the last completed work item. Pulls DORA metrics, summarizes flow, captures keep/stop/start.
argument-hint	[item-id]

Retrospective

Run a team retrospective as defined in .claude/COLLABORATION.md § Team Retrospective (Phase 8).

Usage

/retro -- Retro for the most recently accepted item
/retro 42 -- Retro for a specific item

Workflow

Check escalations. Run ops/feedback-log.sh check-escalations to process any stale proposals before the retro begins.
Gather metrics. Run ops/dora.sh --item <id> (or ops/dora.sh if no item specified) to pull DORA + flow quality data for this iteration.
Summarize the flow. For the target item, report:
- Lead time (promoted → accepted)
- Number of handoff cycles and rework loops
- First-pass yield at each handoff boundary
- Any findings logged during the item's lifecycle
- Bugs found and fixed (count, severity)
- PR metrics: review rounds, time-to-merge (branch created → PR merged), PR comment count
Collect reflections. For each agent that participated in the item, generate a reflection:
- Keep: What worked well and should continue
- Change: What caused friction, rework, or delays
- Try: New approaches to experiment with next iteration
Synthesize. SM consolidates reflections into 3-5 actionable proposals. Each proposal should be:
- Specific (not "communicate better" but "include schema diffs in handoff artifacts")
- Measurable (tied to a metric that will show improvement)
- Scoped (applies to a specific agent, phase, or handoff boundary)
Present to user. Show the metrics summary, agent reflections, and proposals. Ask the user to approve, modify, or defer each proposal.
Apply approved changes. For each approved proposal:
- If it changes an agent's behavior → update the agent's memory or definition
- If it changes a process rule → update .claude/COLLABORATION.md
- If it changes a metric threshold → update fleet-config.json
- Log the retro outcome to findings register
Checkpoint. After applying changes, SM runs Phase 9 (Checkpoint): evaluate pace, assess process health, and determine if a pace promotion or demotion is warranted based on updated metrics.

Output Format

## Retrospective: Item #<id> — <title>

### Metrics
- Lead time: X
- Handoff cycles: X
- First-pass yield: X%
- Bugs: X found, X fixed
- Rework loops: X
- PR review rounds: X
- Time-to-merge: X
- PR comments: X

### Agent Reflections
#### <agent-name>
- Keep: ...
- Change: ...
- Try: ...

### Proposals
1. [proposal] — Metric: [what improves] — Scope: [who/what]
2. ...

### Pace Check
Current: <pace> | Recommended: <pace> | Reason: ...

More from this repository

same repository

behavioral

RD-DCS/venutian-antfarm

Behavioral floor management. Propose changes, review proposals, apply approved changes, view status. Routes to COO as behavioral floor guardian.

2026-03-285

compliance

RD-DCS/venutian-antfarm

Compliance program management. Propose changes, review proposals, apply approved changes, audit conformance, view change log.

2026-03-285

floor

RD-DCS/venutian-antfarm

Generic floor management. Routes to the declared guardian for any governance floor. Use /floor propose <floor-name> <change> to propose changes to any active floor.

2026-03-285

handoff

RD-DCS/venutian-antfarm

Structured agent-to-agent handoff. Validates artifact, logs metrics event, dispatches receiving agent.

2026-03-285

onboard

RD-DCS/venutian-antfarm

Interactive project setup: copy templates, configure fleet, define compliance floor, add first specialist agent.

2026-03-275

RD-DCS/venutian-antfarm

Product Owner commands -- backlog management, prioritization, grooming, review, and status. Routes to the product-owner agent.

2026-03-265

Retrospective

Run a team retrospective as defined in .claude/COLLABORATION.md § Team Retrospective (Phase 8).

Usage

/retro -- Retro for the most recently accepted item

/retro 42 -- Retro for a specific item

Workflow

Check escalations. Run ops/feedback-log.sh check-escalations to process any stale proposals before the retro begins.

Gather metrics. Run ops/dora.sh --item <id> (or ops/dora.sh if no item specified) to pull DORA + flow quality data for this iteration.

Summarize the flow. For the target item, report:

Lead time (promoted → accepted)
Number of handoff cycles and rework loops
First-pass yield at each handoff boundary
Any findings logged during the item's lifecycle
Bugs found and fixed (count, severity)
PR metrics: review rounds, time-to-merge (branch created → PR merged), PR comment count

Collect reflections. For each agent that participated in the item, generate a reflection:

Keep: What worked well and should continue
Change: What caused friction, rework, or delays
Try: New approaches to experiment with next iteration

Synthesize. SM consolidates reflections into 3-5 actionable proposals. Each proposal should be:

Specific (not "communicate better" but "include schema diffs in handoff artifacts")
Measurable (tied to a metric that will show improvement)
Scoped (applies to a specific agent, phase, or handoff boundary)

Present to user. Show the metrics summary, agent reflections, and proposals. Ask the user to approve, modify, or defer each proposal.

Apply approved changes. For each approved proposal:

If it changes an agent's behavior → update the agent's memory or definition
If it changes a process rule → update .claude/COLLABORATION.md
If it changes a metric threshold → update fleet-config.json
Log the retro outcome to findings register

Checkpoint. After applying changes, SM runs Phase 9 (Checkpoint): evaluate pace, assess process health, and determine if a pace promotion or demotion is warranted based on updated metrics.

Output Format

## Retrospective: Item #<id> — <title> ### Metrics - Lead time: X - Handoff cycles: X - First-pass yield: X% - Bugs: X found, X fixed - Rework loops: X - PR review rounds: X - Time-to-merge: X - PR comments: X ### Agent Reflections #### <agent-name> - Keep: ... - Change: ... - Try: ... ### Proposals 1. [proposal] — Metric: [what improves] — Scope: [who/what] 2. ... ### Pace Check Current: <pace> | Recommended: <pace> | Reason: ...