reflectlisted

# Reflect — auto-generate a feature retrospective Produce a single markdown document summarising a finished mumei feature so the team builds institutional knowledge instead of forgetting what happened. ## When to use - The user invokes `/mumei:reflect <feature>` after `/mumei:retire`. - The user invokes it on a `phase: done` feature before archival (rare; lets them edit the reflect.md before retire moves the docs). This skill is `disable-model-invocation: true` — only fires on explicit user request. Never auto-trigger. ## Inputs The skill resolves the feature directory in this order: 1. `.mumei/archive/*/<feature>/` — archived feature 2. `.mumei/specs/<feature>/` — spec vehicle, not yet archived 3. `.mumei/plans/<feature>/` — plan vehicle, not yet archived Refuse with a clear message if none match. ## Method ```bash feature="$1" [[ -n "$feature" ]] || { echo "usage: /mumei:reflect <feature>" >&2; exit 1; } # Resolve feature dir. feature_dir="" for candidate in $(find .mumei/archive -maxdepth 3 -type d -name "$feature" 2>/dev/null) \ ".mumei/specs/${feature}" \ ".mumei/plans/${feature}"; do if [[ -d "$candidate" ]]; then feature_dir="$candidate" break fi done [[ -n "$feature_dir" ]] || { echo "feature not found: $feature" >&2; exit 1; } # Cost-log backfill: if the feature has no cost-log.jsonl yet # (older features may come up empty), try to recover the data from # Claude Code's session logs. Always best-effort — grac