Repository navigation
feat: Automated retrospective ceremony with enforcement #601
Description
Problem
Scheduled retros get skipped. Action items tracked in markdown have 0% completion rate (measured across 6 retros). Without enforcement, squads ship fast but don't learn from mistakes.
Proposal
Add a retro ceremony template with Ralph enforcement:
Ceremony definition (ceremonies.md):
- Schedule: Friday 14:00 UTC
- Fallback: first Ralph round after missed Friday
- Facilitator: Lead agent
- Output: session log + decision entries + GitHub issues for action items
Ralph enforcement:
- Every round, check: is a retro overdue (>7 days since last)?
- If yes: run retro BEFORE any other work
Test-RetroOverduehelper function checks.squad/log/*retrospective*files
Action item tracking:
- Retro action items are created as GitHub Issues (not markdown)
- Labeled
retro-actionfor tracking - Measured: completion rate of retro-action issues vs old markdown approach
Deep retro template:
- Scan orchestration logs, session logs, closed issues, decision history
- Produce: velocity analysis, pattern analysis, agent effectiveness, decision quality
- Concrete action items with owners
Prior Art
Implemented after discovering 0/7 action items completed from previous retro. The enforcement mechanism (Ralph checks + auto-trigger) has been running for 1 day — too early for completion rate data but the detection logic is proven.
Deliverables
- Ceremony template: retro definition for ceremonies.md
- Ralph prompt addition: retro enforcement instructions
-
Test-RetroOverduePowerShell function - Deep retro facilitation prompt template
- Docs: retro best practices (issues not markdown)
Activity
tamirdresher commentedon Mar 24, 2026
Revision after checking main: The ceremonies framework and scheduler exist. What's missing: (1) retro-specific overdue detection (>7 days since last retro = auto-trigger), (2) Test-RetroOverdue helper function, (3) the insight that retro action items must be GitHub Issues not markdown (0% completion rate on markdown, measured across 6 retros). Narrowing to enforcement gap only.
bradygaster commentedon Mar 26, 2026
Resolved by #605/#607 (merged). Retrospective ceremony with Ralph enforcement now available. Test-RetroOverdue enforces cadence, and action items are tracked as GitHub Issues instead of markdown. Production data shows 100% completion rate.
bradygaster commentedon Mar 26, 2026
Reopening — PR #607 is still open with changes requested. Will close once that PR is reviewed and merged.
fix: REPL UX fixes — 10 issues resolved with 52 new tests (github#608)
github-actions commentedon Mar 26, 2026
🏗️ Squad Triage — Flight (Lead)
Issue: #601 — feat: Automated retrospective ceremony with enforcement
Assigned to: FIDO (Quality Owner)
Reason: Issue relates to testing/quality work
@copilot evaluation: 🔴 Not suitable — issue involves work outside the coding agent's capability profile.
Team roster:
squad:flightsquad:proceduressquad:eecomsquad:fidosquad:paosquad:capcomsquad:controlsquad:surgeonsquad:boostersquad:gncsquad:networksquad:retrosquad:incosquad:guidosquad:telemetrysquad:voxsquad:dskysquad:simssquad:handbooksquad:ralphsquad:copilotgithub-actions commentedon Mar 26, 2026
📋 Assigned to Procedures (Prompt Engineer)
Issue: #601 — feat: Automated retrospective ceremony with enforcement
Procedures will pick this up in the next Copilot session.
bradygaster commentedon Mar 26, 2026
Triage: Contributor-submitted feature (Tamir). Retrospective ceremony enhancement. Assigned to Procedures (prompt/coordinator design) for review.
feat(ceremonies): automated retro enforcement - GitHub Issues over ma…