Current State
The detailed Post-PR Mini Retro procedure currently lives in the global CLAUDE.local.md file but hasn't been formalized in the knowledge/procedures directory. The current post-pr-mini-retro.md file is just a 3-line stub that references the continuous improvement principle.
Problem
- The detailed retro questions and agent-led collaborative process are not in a formal procedure file
- The
/retro command only injects continuous-improvement.md, missing the detailed questions
- This violates the single source of truth principle
Proposed Solution
-
Create comprehensive post-pr-mini-retro.md in knowledge/procedures/
- Copy the detailed content from CLAUDE.local.md
- Include all retro questions:
- What worked well?
- What didn't work as expected?
- Procedure adherence
- Systems improvement opportunities
- Formatting overhead check
- Tool boundary clarity
- Principle tensions
- Include the agent-led collaborative process section
- Include personality-driven focus (Jonah, Brent, etc.)
-
Update the retro command template to inject the full procedure:
{{ INJECT:procedures/post-pr-mini-retro.md }}
-
Consider relationship between:
/retro command (general retrospective)
- Post-PR specific retro procedure
- Continuous improvement principle
Benefits
- Single source of truth for retro procedures
- Agents can access detailed retro questions via INJECT pattern
- Follows systems-stewardship principle
- Enables consistent retro experiences
Related
Current State
The detailed Post-PR Mini Retro procedure currently lives in the global CLAUDE.local.md file but hasn't been formalized in the knowledge/procedures directory. The current
post-pr-mini-retro.mdfile is just a 3-line stub that references the continuous improvement principle.Problem
/retrocommand only injectscontinuous-improvement.md, missing the detailed questionsProposed Solution
Create comprehensive post-pr-mini-retro.md in knowledge/procedures/
Update the retro command template to inject the full procedure:
{{ INJECT:procedures/post-pr-mini-retro.md }}Consider relationship between:
/retrocommand (general retrospective)Benefits
Related