| name | babysitter:retrospect |
| description | Analyze a completed or in-flight run and propose process improvements for future runs. |
| argument-hint | [run-id] Optional run ID, defaults to latest run |
babysitter:retrospect
Run a structured retrospective over the last babysitter execution and convert findings into actionable process/library improvements.
Workflow
- Resolve target run
- If run ID is provided, use it.
- Otherwise select the latest run under
.a5c/runs.
- Collect run evidence
- Read run status/events/task outputs:
babysitter run:status .a5c/runs/<runId> --json
babysitter task:list .a5c/runs/<runId> --json
- Inspect trace and event stream:
.a5c/runs/<runId>/run-trace.jsonl.a5c/events/events.jsonl
- Analyze against process library
- Use bundled upstream process library at:
upstream/babysitter/skills/babysit/process
- Compare what was executed vs relevant methodologies/specializations.
- Produce retrospective output
- Include:
- What worked well
- What failed or slowed convergence
- Concrete process modifications (tasks/hooks/policies/budgets/breakpoints)
- Suggested library contributions (processes/skills/agents/docs)
- If user approves, apply improvements
- Update process files under
.a5c/processes and/or codex harness config/docs.
- Suggest contribution flow to upstream Babysitter for generally useful changes.
