retro

# zuvo:retro Generate an engineering retrospective from git history, backlog state, and skill usage trends. Produces a narrative report with actionable items. **Scope:** Post-release or periodic retrospective covering shipping velocity, code churn, backlog health, and quality trends. **Out of scope:** Actually fixing issues (use the suggested zuvo commands in the Actionable Items section). ## Argument Parsing | Input | Action | |-------|--------| | _(empty)_ | Auto-detect window from `memory/last-ship.json` or last two git tags | | `<range>` | Explicit git range, e.g., `v1.0.0..v1.2.0` | | `--since <tag>` | Start of retrospective window (open-ended, through HEAD) | | `--path <dir>` | Scope git analysis to a subdirectory (required for monorepos) | --- ## Environment Compatibility Read `../../shared/includes/env-compat.md` for agent dispatch patterns, path resolution, and progress tracking across Claude Code, Codex, and Cursor. ## Mandatory File Loading ``` CORE FILES LOADED: 1. ../../shared/includes/env-compat.md -- READ 2. ../../shared/includes/run-logger.md -- READ ``` Both files must be read before proceeding. If either is missing, note "DEGRADED -- [file] unavailable" in the report and continue with reduced capability. --- ## Phase 0: Window Detection Determine the retrospective window in this priority order: 1. **Explicit argument** — if `<range>` was provided (e.g., `v1.0.0..v1.2.0`), use it directly. 2. **`--since <tag>`** — if provided, window i...