| 1 | # Ceremonies |
| 2 | |
| 3 | > Team meetings that happen before or after work. Each squad configures their own. |
| 4 | |
| 5 | ## Design Review |
| 6 | |
| 7 | | Field | Value | |
| 8 | |-------|-------| |
| 9 | | **Trigger** | auto | |
| 10 | | **When** | before | |
| 11 | | **Condition** | multi-agent task involving 2+ agents modifying shared systems | |
| 12 | | **Facilitator** | lead | |
| 13 | | **Participants** | all-relevant | |
| 14 | | **Time budget** | focused | |
| 15 | | **Enabled** | ✅ yes | |
| 16 | |
| 17 | **Agenda:** |
| 18 | 1. Review the task and requirements |
| 19 | 2. Agree on interfaces and contracts between components |
| 20 | 3. Identify risks and edge cases |
| 21 | 4. Assign action items |
| 22 | |
| 23 | --- |
| 24 | |
| 25 | ## Retrospective |
| 26 | |
| 27 | | Field | Value | |
| 28 | |-------|-------| |
| 29 | | **Trigger** | auto | |
| 30 | | **When** | after | |
| 31 | | **Condition** | build failure, test failure, or reviewer rejection | |
| 32 | | **Facilitator** | lead | |
| 33 | | **Participants** | all-involved | |
| 34 | | **Time budget** | focused | |
| 35 | | **Enabled** | ✅ yes | |
| 36 | |
| 37 | **Agenda:** |
| 38 | 1. What happened? (facts only) |
| 39 | 2. Root cause analysis |
| 40 | 3. What should change? |
| 41 | 4. Action items for next iteration |
| 42 | |
| 43 | |
| 44 | --- |
| 45 | |
| 46 | ## Retrospective with Enforcement |
| 47 | |
| 48 | | Field | Value | |
| 49 | |-------|-------| |
| 50 | | **Trigger** | auto | |
| 51 | | **When** | weekly | |
| 52 | | **Condition** | No *retrospective* log in .squad/log/ within the last 7 days | |
| 53 | | **Facilitator** | lead | |
| 54 | | **Participants** | all | |
| 55 | | **Time budget** | focused | |
| 56 | | **Enabled** | yes | |
| 57 | | **Enforcement skill** | retro-enforcement | |
| 58 | |
| 59 | **Agenda:** |
| 60 | 1. What shipped this week? (closed issues, merged PRs) |
| 61 | 2. What did not ship? (open issues, blockers) |
| 62 | 3. Root cause on any failures |
| 63 | 4. Action items -- each MUST become a GitHub Issue labeled retro-action |
| 64 | |
| 65 | **Coordinator integration:** |
| 66 | At round start, call Test-RetroOverdue (see skill retro-enforcement). If overdue, run this ceremony before the work queue. |
| 67 | |
| 68 | **Why GitHub Issues, not markdown:** |
| 69 | Production data: 0% completion across 6 retros using markdown checklists, 100% after switching to GitHub Issues. |