Menu
Plan a babysitter workflow without executing it. Focus on creating the best process possible.
| name | babysitter:plan |
| description | Plan a babysitter workflow without executing it. Focus on creating the best process possible. |
| argument-hint | Specific instructions for the plan |
Plan a complex workflow without executing it. This command goes through the full interview and process creation phases but does NOT create a run or execute any tasks.
Same as /babysitter:call:
babysitter skill:discover --plugin-root "$CODEX_PLUGIN_ROOT" --jsonCreate the complete process .js file with all task definitions, quality gates, and convergence loops. Also generate:
<process-name>.diagram.md — Visual process flow diagram<process-name>.process.md — High-level process descriptionPresent the process to the user for review. The process should be complete and ready to run — the user can later execute it with /babysitter:call or /babysitter:yolo.
Store the process files in .a5c/processes/:
.a5c/processes/
├── <process-name>.js # Process definition
├── <process-name>-inputs.json # Default inputs
├── <process-name>.diagram.md # Visual diagram
└── <process-name>.process.md # Description
Do NOT create a run. The plan is the deliverable.
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".
Help and documentation for babysitter commands, processes, skills, agents, and methodologies.
Install or refresh a team-pinned babysitter runtime/content setup from lockfile.
Start a babysitter orchestration run. Use this command to start babysitting a complex workflow.
Analyze a completed or in-flight run and propose process improvements for future runs.
System and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.