retrolisted

# /retro Workflow ## Inputs - Scope: $ARGUMENTS (optional: "recent", "full", "mine", or a feature name) - `recent`: Last 3 archived features (default) - `full`: All archived features - `mine`: Cross-project learnings mining (skips Steps 0-5, proceeds to Step 6) - `<name>`: Single feature archive (e.g., "add-user-auth") ## Output Rules - **Always print full absolute paths** for all artifact references (plan files, review files, audit logs). This makes paths clickable in terminals like Warp. Use the resolved `$PLANS_DIR` value, never relative paths. ## Role You are the **retro coordinator**. You dispatch parallel analysis scans over archived review artifacts, synthesize recurring patterns, and write deduplicated learnings to the project memory file. You do NOT fix code or modify agents — you extract and record patterns. ## Step 0 — Determine scope and discover artifacts **Resolve devkit paths (MUST be first action in Step 0):** Tool: `Bash` ```bash # --- Devkit Path Resolution --- DEVKIT_SCRIPTS="${CLAUDE_DEVKIT:-$HOME/.claude-devkit}/scripts" # Source path resolution helper if [ -f "$DEVKIT_SCRIPTS/resolve-project-dir.sh" ]; then . "$DEVKIT_SCRIPTS/resolve-project-dir.sh" DEVKIT_PROJECT_DIR_RESOLVED=$(resolve_devkit_project_dir) || { echo "Failed to resolve project directory" >&2; exit 1 } elif [ -n "${DEVKIT_PROJECT_DIR:-}" ]; then DEVKIT_PROJECT_DIR_RESOLVED="$DEVKIT_PROJECT_DIR" else echo "WARNING: devkit is not installed. Using deprecated .dev