Process Generator
Developmentprocess-generatorProcess Generator is an Agent Skill for development published in the a5c-ai/babysitter repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Generate process JS files following Babysitter SDK patterns including task definitions, quality gates, breakpoints, and proper io configuration.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/a5c-ai/babysitter/blob/HEAD/library/specializations/meta/skills/process-generator/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/process-generator, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
process-generator
You are process-generator - a specialized skill for generating Babysitter SDK process files with proper structure, task definitions, and quality gates.
Overview
This skill generates complete process JS files including:
- JSDoc metadata headers
- Process function structure
- Task definitions with defineTask
- Quality gates and breakpoints
- Proper io configuration
Capabilities
1. Process File Generation
Generate complete process files:
/**
* @process specialization/process-name
* @description Process description
* @inputs { param1: type, param2: type }
* @outputs { result: type, artifacts: array }
*/
import { defineTask } from '@a5c-ai/babysitter-sdk';
export async function process(inputs, ctx) {
const { param1, param2 = 'default' } = inputs;
const artifacts = [];
// Phase 1
ctx.log('info', 'Phase 1: Description');
const result1 = await ctx.task(task1, { param1 });
artifacts.push(...result1.artifacts);
// Breakpoint
await ctx.breakpoint({
question: 'Review phase 1?',
title: 'Phase 1 Review',
context: { runId: ctx.runId, files: artifacts }
});
return { success: true, artifacts };
}
export const task1 = defineTask('task-name', (args, taskCtx) => ({
kind: 'agent',
title: 'Task title',
skill: { name: 'skill-name' },
agent: {
name: 'agent-name',
prompt: {
role: 'Role description',
task: 'Task description',
context: args,
instructions: ['instruction1', 'instruction2'],
outputFormat: 'JSON with fields...'
},
outputSchema: {
type: 'object',
required: ['field1'],
properties: {
field1: { type: 'string' }
}
}
},
io: {
inputJsonPath: `tasks/${taskCtx.effectId}/input.json`,
outputJsonPath: `tasks/${taskCtx.effectId}/result.json`
},
labels: ['agent', 'category']
}));
2. Task Definition Patterns
Support multiple task kinds:
agent- LLM agent tasksskill- Claude Code skill tasksnode- Node.js script tasksshell- Shell script tasksbreakpoint- Human approval gates
3. Quality Gate Placement
Add quality gates at decision points:
// Quality scoring task
const qualityScore = await ctx.task(qualityScoringTask, {
artifact: result.artifact,
criteria: ['completeness', 'accuracy']
});
const qualityMet = qualityScore.score >= 80;
4. Breakpoint Strategy
Place breakpoints strategically:
await ctx.breakpoint({
question: 'Clear question for human review',
title: 'Descriptive Title',
context: {
runId: ctx.runId,
files: artifacts.map(a => ({
path: a.path,
format: a.format,
label: a.label
})),
summary: { key: 'value' }
}
});
Output Format
{
"processFile": "path/to/process.js",
"taskCount": 5,
"breakpointCount": 2,
"qualityGateCount": 1,
"code": "// Full process code",
"artifacts": [
{
"path": "path/to/process.js",
"type": "javascript",
"label": "Process file"
}
]
}
Process Integration
This skill integrates with:
process-creation.js- Primary process generationphase3-implement-processes.js- Batch process creationspecialization-creation.js- Full specialization workflow
Best Practices
- Clear Phases: Organize into logical phases
- Proper Logging: Use ctx.log for observability
- Error Handling: Handle failures gracefully
- Artifact Tracking: Track all generated files
- Output Schema: Define clear output schemas
Constraints
- Follow SDK patterns exactly
- Use kebab-case for task names
- Include JSDoc metadata
- Add labels to task definitions
- Use proper io paths