retro

name	retro
description	Friday retrospective and next week planning. Collects wins, lessons, unresolved issues. Looks ahead at deadlines and opportunities. Drafts next week priorities. Octopus colors: Purple (synthesis) + Yellow (forward intelligence).

/retro: Friday Retrospective and Next Week Plan

Octopus Colors: Purple (Manager) + Yellow (Researcher)

Process

1. Collect the week's results (Purple):
   • Read all reports from .chairman/reports/ dated this week
   • Read completed assignments from .chairman/assignments/
   • Identify: what shipped, what was learned, what broke, what surprised
2. Compile wins (for morale and marketing potential)
3. Compile lessons (for knowledge base)
4. List unresolved issues (carry forward to next week)
5. Look ahead (Yellow):
   • Upcoming deadlines or commitments
   • Scheduled meetings or events
   • Pipeline stage changes (deals advancing or stalling)
   • Seasonal or market patterns
6. Draft next week priorities (Purple):
   • Top 3 objectives
   • Department assignments
   • Approval gates the Chairman should expect

Output Format

# Week in Review: [Date Range]

## Wins
- [What went well, with specifics]

## Lessons Learned
- [What we learned, what to do differently]

## Unresolved
- [Carried forward to next week]

## Next Week: [Date Range]

### Top 3 Priorities
1. [Priority]: [Which department, what outcome expected]
2. [Priority]: [Which department, what outcome expected]
3. [Priority]: [Which department, what outcome expected]

### Upcoming
- [Deadlines, meetings, events]

### Expected Approval Gates
- [What the Chairman will need to review/decide]

## Chairman Action
[ ] Approve priorities as-is
[ ] Adjust priorities: ___
[ ] Add priority: ___

Rules

• Keep it honest. Include failures and surprises, not just wins.
• Lessons should be actionable, not vague ("improve communication" is useless; "add approval gate for external content" is useful).
• Save to .chairman/reports/retro-YYYY-MM-DD.md
• Update .chairman/state.json with week-end status.
• If any lessons should become permanent knowledge, run /knowledge next.