solo-retro

# /retro This skill is self-contained — follow the phases below instead of delegating to other skills (/review, /audit, /build) or spawning Task subagents. Run all analysis directly. Post-pipeline retrospective. Parses pipeline logs, counts productive vs wasted iterations, identifies recurring failure patterns, scores the pipeline run, and suggests concrete patches to skills/scripts to prevent the same failures next time. ## Live Context - Branch: !`git branch --show-current 2>/dev/null` - Recent commits: !`git log --oneline -10 2>/dev/null` - Modified files: !`git diff --name-only HEAD~5..HEAD 2>/dev/null | head -20` ## When to use After a pipeline completes (or gets cancelled). This is the process quality check — `/review` checks **code quality**, `/retro` checks **pipeline process quality**. Can also be used standalone on any project — with or without pipeline logs. ## MCP Tools (use if available) - `session_search(query)` — find past pipeline runs and known issues - `codegraph_explain(project)` — understand project architecture context - `codegraph_query(query)` — query code graph for project metadata If MCP tools are not available, fall back to Glob + Grep + Read. ## Phase 1: Locate Artifacts 1. **Detect project** from `$ARGUMENTS` or CWD: - If argument provided: use it as project name - Otherwise: extract from CWD basename (e.g., `~/projects/my-app` -> `my-app`) 2. **Find pipeline state file:** `.solo/pipelines/solo-pipeline-{project}.local.md` (projec...