retrospect-external-babysitter-run

# Retrospect External Babysitter Run Analyse a babysitter run that lives in an external public repository, using the same lens as the in-repo `/babysitter:retrospect` command. Produce a written retrospective with concrete suggestions for the process author (or, if the insight generalizes, for the babysitter project itself). ## When to use - User names an external repo and asks for a retrospective. - User asks "find a babysitter run to retrospect on" (combine with the `catalog-babysitter-users` skill to pick one). - User asks "how are other people using babysitter processes? What do they get wrong?". ## Prerequisites - `gh` CLI authenticated. - `docs/repo-with-babysitter-processes.md` exists (if not, run the `catalog-babysitter-users` skill first). - A workspace directory where external repos can be shallow-cloned (default: `/tmp/babysitter-retrospect/` or `.a5c/tmp/external-runs/`). ## Phase 1 -- Target selection 1. Read `docs/repo-with-babysitter-processes.md` and list Active repos with stars + description. If the user already named a repo, skip to step 3. 2. Ask the user which repo to retrospect on (use AskUserQuestion in interactive mode; if non-interactive, pick the highest-starred Active repo that wasn't retrospected in the last 30 days -- track via `docs/retrospectives/<owner>-<name>/log.md`). 3. Confirm the target with the user before cloning. ## Phase 2 -- Discover processes and runs Shallow clone the target: ```bash mkdir -p .a5c/tmp/external-runs cd .a5c/t...