Setting the file. One moment.
Team meetings that happen before or after work. Each squad configures their own.
Trigger
| Condition | multi-agent task involving 2+ agents modifying shared systems |
- Review the task and requirements
- Agree on interfaces and contracts between components
- Identify risks and edge cases
- Assign action items
- What happened? (facts only)
- Root cause analysis
- What should change?
- Action items for next iteration
- What shipped this week? (closed issues, merged PRs)
- What did not ship? (open issues, blockers)
- Root cause on any failures
- Action items – each MUST become a GitHub Issue labeled retro-action
Coordinator integration:
At round start, call Test-RetroOverdue (see skill retro-enforcement). If overdue, run this ceremony before the work queue.
Why GitHub Issues, not markdown:
Production data: 0% completion across 6 retros using markdown checklists, 100% after switching to GitHub Issues.
ceremonies.md