/retro

Meta-analysis of OODA system performance. Analyzes what's working, what's not, suggests rule updates and cleanups.

Usage

/retro

No arguments. Analyzes full system state.

Process

1. Dispatch Observe agents (parallel):

   • State analysis: .antmachine/*/state.json
   • Plan patterns: rejection rates, selection history
   • Execution patterns: failures, observation loops, blockers
   • Artifact health: ages, sizes, orphans
   • Previous retros: recurring patterns

2. Synthesize observations into report:

   • What's Working
   • What's Not Working
   • Blockers Identified
   • Usage Tips
   • Suggested Rule Updates
   • Suggested Cleanups

3. Present rule updates with numbered options:

   Create rules? [1] [2] [both] [none]
   

4. Present cleanup suggestions with numbered options:

   Perform cleanups? [1] [2] [3] [all] [none]
   

5. Execute approved actions only

6. Log to .antmachine/retros/{timestamp}.md

Output Format

# Retrospective - {timestamp}

## What's Working
## What's Not Working
## Blockers Identified
## Usage Tips

## Suggested Rule Updates
1. **{filename}** - {reason}
   Pattern: {evidence}

Create rules? [1] [2] [both] [none]

## Suggested Cleanups
1. {action} ({impact})

Perform cleanups? [1] [2] [3] [all] [none]

## Actions Taken
- [x] Created rule
- [ ] Declined cleanup

Rules

• Uses Observe agents to gather data (consistent with architecture)
• Never auto-executes destructive actions
• User selects from numbered options
• Logs everything for future retros to analyze
• Rules created go to .claude/rules/ (Claude Code project rules)

When to Run

• After completing a complex feature
• When hitting repeated blockers
• Periodically to maintain system health
• When the system suggests it after a difficult session