← ClaudeAtlas

retrolisted

Retrospective — feed the causes of rework, failures, CEO intervention and incidents back into rules, skills or guardrails
jaewhi-park/GARAGISTE · ★ 1 · AI & Automation · score 75
Install: claude install-skill jaewhi-park/GARAGISTE
Run a retrospective. Subject: $ARGUMENTS (plan slug, session or incident) 1. Look at the recent trend in docs/METRICS.md first (rework, questions, duration), then pinpoint at most three places where rework, verification failures, review blockers, CEO intervention or incidents occurred, and write the root cause of each. 2. Propose a countermeasure per cause and say where it belongs: one line in CLAUDE.md / a skill change / a guardrail hook (hard block) / the plan format / agent memory / a new role via `/recruit` (only for a new permission boundary or a separate judge). 3. Have team-planner apply only what the CEO approves. Add rules only for things that actually went wrong.