Retro

5. Completeness Check

Before writing, self-audit the retrospective. For each of the 10 sections:

If any section is empty: Go back to Step 3 and ask the user via manual provider. Do not write a retrospective with blank sections.

Manual question minimums by data richness:

• If GSD or GitHub provide structured data: minimum 3 manual questions.
• If only git and manual are active: minimum 5 manual questions (git provides metrics but not subjective context).
• If only manual is active: minimum 7 manual questions (you are the sole data source besides the user).

Go back and ask about surprises, failures, forward risks, edge cases, and decisions at minimum.

6. Write the Retrospective

Save to <retrospective_dir>/phase-<N>-<slug>.md (default: .jira/sprints/<active-slug>/ if jira-managed, otherwise .project/retros/). Overwrite if exists.

Slug derivation: Phase name lowercased, spaces replaced with hyphens, non-alphanumeric characters (except hyphens) removed, truncated to 50 characters. If no phase name exists, use phase number only: phase-<N>.md.

7. Update Cumulative Summary

If summary_tracker.auto_update is true, update <retrospective_dir>/SUMMARY.md:

• Phase column in project-level metrics table
• Phase completion status (status, confidence, key outcome)
• Cross-phase learnings (recurring themes, compounding risks)
• Cumulative risk register
• Project-level decisions

If SUMMARY.md doesn't exist, create from built-in default at _templates/SUMMARY-TEMPLATE.md.

8. Generate Stakeholder Report

If stakeholder_report.auto_generate is true, generate <retrospective_dir>/phase-<N>-<slug>-stakeholder.md from _templates/STAKEHOLDER-REPORT-TEMPLATE.md:

• Plain language, no jargon
• Lead with outcomes and numbers
• Risks and blockers up front
• Next phase preview with readiness assessment

Hook Enforcement

The skill ships with hooks/retro-trigger.sh — a real Claude Code PostToolUse hook, not just instructions.

What It Detects

Behavior by Mode

• auto: Prints [retro] Phase N complete. Auto-generating retrospective... to stderr (exit 2). The agent sees this as a hook message and should run /retro.
• prompt: Prints the prompt message and writes pending_retro to config. User decides when to run /retro.
• manual: Hook exits 0 silently. No-op.

Registration

The hook must be registered in the project's .claude/settings.json:

{
  "hooks": {
    "PostToolUse": [
      {
        "matcher": "Edit|Write|Bash",
        "hooks": [
          {
            "type": "command",
            "command": "~/.claude/hooks/retro-trigger.sh",
            "timeout": 10
          }
        ]
      }
    ],
    "SessionStart": [
      {
        "matcher": "",
        "hooks": [
          {
            "type": "command",
            "command": "~/.claude/hooks/retro-reminder.sh",
            "timeout": 5
          }
        ]
      }
    ]
  }
}

On /retro init, register both hooks automatically if the project's .claude/settings.json doesn't already have them. Merge into existing hook arrays — do not overwrite existing hooks for the same trigger.

Two hooks, two jobs:

• retro-trigger.sh (PostToolUse) — detects phase completion in real time
• retro-reminder.sh (SessionStart) — reminds about deferred retros on session start

See references/config.md for pending_retro schema.

Reference Files

• references/config.md — Full config schema, field reference, first-run initialization logic
• references/providers.md — Data provider details, probe logic, what each reads, precedence rules
• _templates/PHASE-RETRO-TEMPLATE.md — Default phase retrospective template
• _templates/STAKEHOLDER-REPORT-TEMPLATE.md — Default stakeholder report template
• _templates/SUMMARY-TEMPLATE.md — Default cumulative summary template