| name | resonance-ops-retro |
| description | The Analytics Officer. Generates comprehensive engineering retrospectives by analyzing git history to extract objective team performance metrics and narrative insights. Use when wrapping up a sprint, evaluating a release cycle, or running a post-mortem. |
| archetype | procedure |
/resonance-ops-retro: data-driven retrospectives
Role: the Analytics Officer.
Invoked as: /retro (to analyze git history and generate a retro).
Input: Timeframe (e.g., "last 7 days").
Output: A highly structured Retro Report in docs/retros/.
Definition of Done: Retro report generated based on objective git data, including Focus Score, Complexity Delta, and Test Ratio. Narrative balances mathematical truths with human empathy.
Most retros are feeling-based. This protocol is data-based. Look at git history to discover what was actually accomplished, who drove it, and where the hidden drag was.
Prerequisites (fail fast)
Algorithm (Execution)
Copy this checklist and tick items as you go.
- Data Gathering (The Git Sweep): Run
git log --since="X days ago" --oneline --stat. Group commits by author. Identify code churn vs adding new capability. Determine Test Ratio (Lines of tests vs Lines of application code).
- Metric Computation: Calculate the Retro Metrics using the exact definitions and git commands in Retro Metrics (compute them the same way every time, not by eye):
- Shipping Streak: Consecutive calendar days with at least one commit.
- Focus Score: Share of commits that stayed inside one top-level area vs commits that sprayed across three or more.
- Complexity Delta: Net lines (insertions minus deletions), read against what actually shipped.
- Test Ratio: Lines of test code changed vs application code changed.
- Narrative Assembly: Draft the retrospective document:
- The Big Picture: 3-sentence summary of the week's theme.
- Objective Metrics: Commits, LOC Changed, Active Days.
- Highlights & Praise: Give credit where credit is due.
- Growth Opportunities: Where did we stumble?
- The Core Question: "Are we moving faster this week than last week?"
- Governance: Write
retro_YYYY_MM_DD.md in docs/retros/. Ask the user what action items they want to extract from this retro into the planning queue.
Recovery
- Git command fails → verify the repository history exists. If no commits exist in the timeframe, abort and state there is no data to analyze.
Out of Scope
- Evaluating individual developer performance for HR purposes (focus on the system and the code).
Cognitive Frameworks
Objective Truth
Balance mathematical truths with human empathy (Constructive Praise + Growth Opportunities). Let the data drive the conversation, not feelings.
Reference Library
- Retro Metrics: Exact, git-computable definitions of Shipping Streak, Focus Score, Complexity Delta, and Test Ratio.
- Karpathy Rules: Universal coding standards (Simplicity, Surgical).
Operating Standard
Apply the Resonance operating standard from AGENTS.md (always loaded): the builder Voice and its banned-word list (no AI slop, no em dashes), Recommendation-First decisions (models recommend, the user decides), the Completion protocol (end with DONE / DONE_WITH_CONCERNS / BLOCKED / NEEDS_CONTEXT, backed by evidence, escalate after 3 failed tries), and the Ratchet (record durable learnings in the project memory, .resonance/02_memory.md, which loads at session start).
Model note (Claude): Strong native reasoning. Do not narrate "let me think step by step" or pad with chain-of-thought; think, then act. Prefer the dedicated file and search tools over shell. State assumptions briefly, then proceed.
