babysitter:retrospect

Analyze a completed or in-flight run and propose process improvements for future runs.

509 stars

Best use case

babysitter:retrospect is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Analyze a completed or in-flight run and propose process improvements for future runs.

Teams using babysitter:retrospect should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/retrospect/SKILL.md --create-dirs "https://raw.githubusercontent.com/a5c-ai/babysitter/main/plugins/babysitter-codex/.codex/skills/babysitter/retrospect/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/retrospect/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How babysitter:retrospect Compares

Feature / Agent	babysitter:retrospect	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Analyze a completed or in-flight run and propose process improvements for future runs.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# babysitter:retrospect

Run a structured retrospective over the last babysitter execution and convert findings into actionable process/library improvements.

## Workflow

1. Resolve target run
- If run ID is provided, use it.
- Otherwise select the latest run under `.a5c/runs`.

2. Collect run evidence
- Read run status/events/task outputs:
```bash
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`

3. Analyze against process library
- Use bundled upstream process library at:
  - `upstream/babysitter/skills/babysit/process`
- Compare what was executed vs relevant methodologies/specializations.

4. 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)

5. 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.

Related Skills

babysitter

509

from a5c-ai/babysitter

Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)

retrospect

509

from a5c-ai/babysitter

Summarize or retrospect on a completed Babysitter run.

retrospective-facilitator

509

from a5c-ai/babysitter

Generate retrospective formats and analyze improvement actions

babysitter-codex

509

from a5c-ai/babysitter

Orchestrate complex, multi-step AI workflows with quality convergence loops, event-sourced state, and human-in-the-loop approval gates. Use when the user wants to babysit a task, orchestrate a workflow, run quality-gated development, resume a previous orchestration run, diagnose run health, plan without executing, set up a project or user profile for babysitter, or assimilate an external methodology. Also use when the user mentions "babysitter", "orchestrate", "babysit", "quality loop", or "convergence loop".