Process Library
The Babysitter Process Library is the SDK-managed library under library/. The current generated snapshot counts 2,239 JavaScript process files, including 149 methodology files, 2,038 specialization files, and 31 shared process files, plus support assets such as 2,021 skills and 1,342 agents discovered in the live tree.
In Plain English
Think of the Process Library like a cookbook with 2,239 recipes in the live repository tree.
Just like how a cookbook has recipes for Italian, Mexican, Japanese, and French cuisine - the Process Library has "recipes" for building web apps, mobile apps, APIs, security audits, and much more.
You don't need to read the whole cookbook. Just tell Babysitter what you want to make:
- "Build me a REST API" → Babysitter picks the right recipe automatically
- "Use the TDD methodology" → You pick a specific recipe
Each recipe includes:
- Ingredients (inputs you provide)
- Steps (phases of work)
- Quality checks (tests to ensure it's done right)
- Approval points (places where you review before continuing)
Quick Start: Using the Library
Most users never need to browse the library directly. Just describe what you want:
/babysitter:call build a user authentication system with login, registration, and password reset
Babysitter automatically finds and combines the right processes. Want a specific methodology?
/babysitter:call with TDD methodology, create a REST API for managing tasks
That's it! See the sections below for details on what's available.
What is the Process Library?
The Process Library provides ready-to-use orchestration workflows for virtually any task you might encounter. Each process is:
- Battle-tested: Designed with best practices and quality gates built-in
- Composable: Can be combined with other processes to create complex workflows
- Customizable: Extend or modify any process to match your requirements
- Self-documenting: Includes clear inputs, outputs, and execution flow
Instead of writing orchestration logic from scratch, you can leverage these pre-built processes and focus on what matters: your actual work.
How Babysitter Uses the Process Library
When you describe a task to Babysitter, the agent automatically selects the most relevant processes from the library and adapts them to your specific needs. This happens in several ways:
Automatic Process Selection
Simply describe what you want to accomplish in natural language:
Use babysitter to build a Next.js app with authentication and PostgreSQL
Babysitter will:
- Identify relevant processes (e.g.,
nextjs-fullstack-app,jwt-authentication,database-setup) - Combine and adapt them to your requirements
- Execute the orchestrated workflow with quality gates
Explicit Process Selection
You can also request a specific process by name:
Use babysitter with the tdd-quality-convergence process to implement user authentication
Or:
Use babysitter with the devin methodology to build a REST API
Mix and Match
For complex tasks, Babysitter intelligently combines multiple processes:
Use babysitter to create a microservices architecture with:
- GraphQL gateway
- Kubernetes deployment
- Monitoring and alerting
This might pull from graphql-api-apollo, kubernetes-setup, monitoring-setup, and cicd-pipeline-setup processes, adapting each to work together coherently.
Customizing for Your Use Case
You can also modify existing processes or provide additional context:
Use babysitter with the security-audit process but focus specifically on
OWASP Top 10 vulnerabilities and include PCI-DSS compliance checks
The agent will take the base process and adapt it to your specific requirements.
Library Structure
The built-in library lives under library/. Harness plugins do not ship the whole process tree under skills/babysit/; instead, they expose the babysit skill and rely on the SDK-managed active process-library binding. Project-local copies under .a5c/ are an override layer that can be created by plugins or by you.
How The Layers Relate
- Built-in library:
library/is the canonical source tree for built-in processes, methodologies, shared components, references, and examples. - Plugin package: the harness plugin ships skills, hooks, and packaging files such as
plugins/babysitter-unified/skills/babysit/SKILL.md, then asks the SDK which process-library binding is active. - Project-local
.a5c/copies: files like.a5c/processes/,.a5c/skills/, and.a5c/agents/inside a workspace override the shared library when present.
Active Lookup Order
Babysitter process discovery should prefer:
- Project-local
.a5c/processes/ - The SDK-managed active process-library binding resolved by
babysitter process-library:active --json - Other installed skill/plugin roots only as compatibility fallback
Main Library Areas
Click any link to view the current source location:
| Area | Description | Link |
|---|---|---|
| library/methodologies/ | Methodology families such as Agile, Devin, GSD, Kanban, Spec-Kit, and more | Browse → |
| library/methodologies/gsd/ | Get Shit Done workflows | Browse → |
| library/specializations/ | Domain-specific processes across the specialization tree | Browse → |
| library/processes/shared/ | Shared reusable process components | Browse → |
| library/tdd-quality-convergence.js | Featured TDD workflow at the library root | library/tdd-quality-convergence.js |
Specializations Sub-Structure
| Category | Description | Link |
|---|---|---|
| Development and technical specializations | Web, mobile, DevOps, AI, security, collaboration, authoring, and more | Browse → |
| domains/business/ | Finance, HR, marketing, sales, legal, logistics, and related business domains | Browse → |
| domains/science/ | Physics, chemistry, engineering, mathematics, scientific discovery, and related domains | Browse → |
| domains/social-sciences-humanities/ | Education, healthcare, philosophy, arts, and social-science research workflows | Browse → |
| meta/ | Process creation, validation, and library tooling | Browse → |
Browsing and Discovering Processes
Asking Claude
The easiest way to discover processes is to ask Claude:
What processes are available for web development?
Show me security-related processes in the babysitter library
Claude can browse the process library and recommend the best match for your needs.
Process Naming Convention
Process files follow a consistent naming pattern:
feature-name.js- The process definitionREADME.md- Category documentationexamples/- Example inputs and usageagents/- Specialized agents for the category
Finding the Right Process
- Start with the category that matches your domain
- Review the README.md in that category for an overview
- Check the JSDoc at the top of each
.jsfile for inputs/outputs - Look at examples/ for sample usage patterns
Generated Catalog Snapshot
The catalog data in this section is refreshed from the live library/ tree. The explanatory prose on this page remains hand-written.
Snapshot refreshed from the live library/ tree on 2026-05-07.
- Current snapshot counts
- Methodology families
- Shared process groups
- Development and technical specializations
- Business domains
- Science domains
- Social sciences and humanities domains
- Largest specialization categories
Current Snapshot Counts
| Area | Current Count | Source |
|---|---|---|
All library .js process files | 2,239 | library/ |
| Methodology directories | 38 | library/methodologies/ |
Methodology .js process files | 149 | library/methodologies/ |
Shared .js process files | 31 | library/processes/shared/ |
Specialization .js process files | 2,038 | library/specializations/ |
| Top-level specialization directories | 39 | library/specializations/ |
| Development and technical specialization processes | 837 | library/specializations/ |
| Business-domain specialization processes | 490 | library/specializations/domains/business/ |
| Science-domain specialization processes | 551 | library/specializations/domains/science/ |
| Social-sciences-and-humanities specialization processes | 160 | library/specializations/domains/social-sciences-humanities/ |
| Skill definition files | 2,021 | library/ |
| Agent definition files | 1,342 | library/ |
| README files under library | 1,816 | library/ |
Methodology Families
| Methodology | Processes | Browse |
|---|---|---|
superpowers | 15 | Browse → |
gsd | 14 | Browse → |
bmad-method | 6 | Browse → |
ccpm | 6 | Browse → |
maestro | 6 | Browse → |
metaswarm | 6 | Browse → |
rpikit | 6 | Browse → |
cc10x | 5 | Browse → |
claudekit | 5 | Browse → |
cog-second-brain | 5 | Browse → |
everything-claude-code | 5 | Browse → |
gastown | 5 | Browse → |
pilot-shell | 5 | Browse → |
ruflo | 5 | Browse → |
automaker | 4 | Browse → |
planning-with-files | 4 | Browse → |
spec-kit | 4 | Browse → |
atdd-tdd | 1 | Browse → |
bdd-specification-by-example | 1 | Browse → |
cleanroom | 1 | Browse → |
domain-driven-design | 1 | Browse → |
double-diamond | 1 | Browse → |
event-storming | 1 | Browse → |
example-mapping | 1 | Browse → |
extreme-programming | 1 | Browse → |
feature-driven-development | 1 | Browse → |
hypothesis-driven-development | 1 | Browse → |
impact-mapping | 1 | Browse → |
jobs-to-be-done | 1 | Browse → |
kanban | 1 | Browse → |
ontology-driven-development | 1 | Browse → |
process-hardening | 1 | Browse → |
rup | 1 | Browse → |
scrum | 1 | Browse → |
shape-up | 1 | Browse → |
spiral-model | 1 | Browse → |
v-model | 1 | Browse → |
waterfall | 1 | Browse → |
Shared Process Groups
| Group | Processes | Browse |
|---|---|---|
ci | 5 | Browse → |
communication | 3 | Browse → |
local-dev | 2 | Browse → |
analysis | 1 | Browse → |
release | 1 | Browse → |
reporting | 1 | Browse → |
Development and Technical Specializations
| Category | Processes | Browse |
|---|---|---|
web-development | 61 | Browse → |
algorithms-optimization | 45 | Browse → |
ai-agents-conversational | 43 | Browse → |
cryptography-blockchain | 33 | Browse → |
security-research | 32 | Browse → |
meta | 31 | Browse → |
cli-mcp-development | 30 | Browse → |
game-development | 30 | Browse → |
network-programming | 30 | Browse → |
performance-optimization | 30 | Browse → |
robotics-simulation | 30 | Browse → |
devops-sre-platform | 29 | Browse → |
embedded-systems | 26 | Browse → |
mobile-development | 26 | Browse → |
security-compliance | 26 | Browse → |
code-migration-modernization | 25 | Browse → |
fpga-programming | 25 | Browse → |
gpu-programming | 25 | Browse → |
programming-languages | 25 | Browse → |
sdk-platform-development | 25 | Browse → |
desktop-development | 24 | Browse → |
ux-ui-design | 24 | Browse → |
technical-documentation | 21 | Browse → |
qa-testing-automation | 20 | Browse → |
software-architecture | 20 | Browse → |
product-management | 19 | Browse → |
collaboration | 18 | Browse → |
data-engineering-analytics | 18 | Browse → |
data-science-ml | 18 | Browse → |
media | 7 | Browse → |
observability | 5 | Browse → |
research | 5 | Browse → |
communication | 4 | Browse → |
common-utilities | 3 | Browse → |
authoring | 2 | Browse → |
business | 1 | Browse → |
sourcing | 1 | Browse → |
Business Domains
| Category | Processes | Browse |
|---|---|---|
knowledge-management | 36 | Browse → |
decision-intelligence | 33 | Browse → |
legal | 28 | Browse → |
business-strategy | 26 | Browse → |
operations | 26 | Browse → |
business-analysis | 25 | Browse → |
entrepreneurship | 25 | Browse → |
finance-accounting | 25 | Browse → |
logistics | 25 | Browse → |
marketing | 25 | Browse → |
project-management | 25 | Browse → |
public-relations | 25 | Browse → |
sales | 25 | Browse → |
supply-chain | 25 | Browse → |
venture-capital | 25 | Browse → |
human-resources | 24 | Browse → |
digital-marketing | 23 | Browse → |
business-strategy-advanced | 22 | Browse → |
customer-experience | 20 | Browse → |
travel | 2 | Browse → |
Science Domains
| Category | Processes | Browse |
|---|---|---|
scientific-discovery | 168 | Browse → |
quantum-computing | 27 | Browse → |
mechanical-engineering | 26 | Browse → |
aerospace-engineering | 25 | Browse → |
automotive-engineering | 25 | Browse → |
biomedical-engineering | 25 | Browse → |
chemical-engineering | 25 | Browse → |
civil-engineering | 25 | Browse → |
computer-science | 25 | Browse → |
environmental-engineering | 24 | Browse → |
materials-science | 24 | Browse → |
mathematics | 24 | Browse → |
physics | 24 | Browse → |
industrial-engineering | 23 | Browse → |
electrical-engineering | 21 | Browse → |
bioinformatics | 20 | Browse → |
nanotechnology | 20 | Browse → |
Social Sciences and Humanities Domains
| Category | Processes | Browse |
|---|---|---|
arts-culture | 35 | Browse → |
philosophy | 26 | Browse → |
education | 25 | Browse → |
humanities | 25 | Browse → |
social-sciences | 25 | Browse → |
healthcare | 24 | Browse → |
Largest Specialization Categories
| Category | Processes | Browse |
|---|---|---|
scientific-discovery | 168 | Browse → |
web-development | 61 | Browse → |
algorithms-optimization | 45 | Browse → |
ai-agents-conversational | 43 | Browse → |
knowledge-management | 36 | Browse → |
arts-culture | 35 | Browse → |
cryptography-blockchain | 33 | Browse → |
decision-intelligence | 33 | Browse → |
security-research | 32 | Browse → |
meta | 31 | Browse → |
cli-mcp-development | 30 | Browse → |
game-development | 30 | Browse → |
Example Processes by Category
Web Development
Browse all web-development processes →
| Process | Description | Source |
|---|---|---|
| nextjs-fullstack-app | Complete Next.js application | library/specializations/web-development/nextjs-fullstack-app.js |
| graphql-api-apollo | GraphQL API with Apollo | library/specializations/web-development/graphql-api-apollo.js |
| jwt-authentication | JWT auth implementation | library/specializations/web-development/jwt-authentication.js |
| e2e-testing-playwright | Playwright E2E testing | library/specializations/web-development/e2e-testing-playwright.js |
| micro-frontend-module-federation | Micro-frontend architecture | library/specializations/web-development/micro-frontend-module-federation.js |
| accessibility-audit-remediation | WCAG compliance | library/specializations/web-development/accessibility-audit-remediation.js |
| docker-containerization | Docker deployment | library/specializations/web-development/docker-containerization.js |
AI Agents and Conversational
Browse all ai-agents-conversational processes →
| Process | Description | Source |
|---|---|---|
| multi-agent-system | Multi-agent orchestration | library/specializations/ai-agents-conversational/multi-agent-system.js |
| advanced-rag-patterns | Advanced RAG implementation | library/specializations/ai-agents-conversational/advanced-rag-patterns.js |
| langgraph-workflow-design | LangGraph workflows | library/specializations/ai-agents-conversational/langgraph-workflow-design.js |
| conversational-memory-system | Long-term memory for agents | library/specializations/ai-agents-conversational/conversational-memory-system.js |
| function-calling-agent | Tool-using agents | library/specializations/ai-agents-conversational/function-calling-agent.js |
| agent-evaluation-framework | Agent testing and eval | library/specializations/ai-agents-conversational/agent-evaluation-framework.js |
| llm-observability-monitoring | LLM monitoring setup | library/specializations/ai-agents-conversational/llm-observability-monitoring.js |
Security Research
Browse all security-research processes →
| Process | Description | Source |
|---|---|---|
| binary-reverse-engineering | Binary analysis | library/specializations/security-research/binary-reverse-engineering.js |
| exploit-development | Exploit writing workflow | library/specializations/security-research/exploit-development.js |
| fuzzing-campaign | Fuzzing setup and execution | library/specializations/security-research/fuzzing-campaign.js |
| malware-analysis | Malware analysis workflow | library/specializations/security-research/malware-analysis.js |
| network-penetration-testing | Network pentesting | library/specializations/security-research/network-penetration-testing.js |
| capture-the-flag-challenges | CTF solving workflow | library/specializations/security-research/capture-the-flag-challenges.js |
| bug-bounty-workflow | Bug bounty methodology | library/specializations/security-research/bug-bounty-workflow.js |
DevOps and SRE
Browse all devops-sre-platform processes →
| Process | Description | Source |
|---|---|---|
| kubernetes-setup | Kubernetes cluster setup | library/specializations/devops-sre-platform/kubernetes-setup.js |
| cicd-pipeline-setup | CI/CD pipeline creation | library/specializations/devops-sre-platform/cicd-pipeline-setup.js |
| monitoring-setup | Observability stack | library/specializations/devops-sre-platform/monitoring-setup.js |
| incident-response | Incident management | library/specializations/devops-sre-platform/incident-response.js |
| disaster-recovery-plan | DR planning and testing | library/specializations/devops-sre-platform/disaster-recovery-plan.js |
| slo-sli-tracking | SLO/SLI implementation | library/specializations/devops-sre-platform/slo-sli-tracking.js |
| secrets-management | Secrets management setup | library/specializations/devops-sre-platform/secrets-management.js |
Scientific Discovery
Browse all scientific-discovery processes →
| Process | Description | Source |
|---|---|---|
| hypothesis-formulation-testing | Scientific method | library/specializations/domains/science/scientific-discovery/hypothesis-formulation-testing.js |
| causal-inference | Causal analysis | library/specializations/domains/science/scientific-discovery/causal-inference.js |
| bayesian-probabilistic-reasoning | Bayesian reasoning | library/specializations/domains/science/scientific-discovery/bayesian-probabilistic-reasoning.js |
| experimental-design-reasoning | Experiment planning | library/specializations/domains/science/scientific-discovery/experimental-design-reasoning.js |
| literature-review-synthesis | Literature review | library/specializations/domains/science/scientific-discovery/literature-review-synthesis.js |
| reproducible-research-pipeline | Reproducibility | library/specializations/domains/science/scientific-discovery/reproducible-research-pipeline.js |
| systems-thinking | Systems analysis | library/specializations/domains/science/scientific-discovery/systems-thinking.js |
Using a Pre-Built Process
Recommended: Just use /babysitter:call <request> - it selects the right process automatically:
/babysitter:call build a Next.js app with authentication, PostgreSQL database, and Vercel deployment
Babysitter will find the nextjs-fullstack-app process and configure it based on your request.
Customizing Processes
Extending an Existing Process
import { process as baseProcess } from '../../../library/specializations/web-development/nextjs-fullstack-app.js';
export async function process(inputs, ctx) {
// Add pre-processing
const enhancedInputs = {
...inputs,
additionalChecks: true,
customConfig: myConfig
};
// Run base process
const result = await baseProcess(enhancedInputs, ctx);
// Add post-processing
await ctx.task(myCustomValidation, result);
return {
...result,
customData: myCustomData
};
}
Composing Multiple Processes
import { process as planPhase } from '../../../library/methodologies/gsd/plan-phase.js';
import { process as executePhase } from '../../../library/methodologies/gsd/execute-phase.js';
import { process as tddConvergence } from '../../../library/tdd-quality-convergence.js';
export async function process(inputs, ctx) {
// Planning with GSD
const plan = await planPhase(inputs, ctx);
// Execute with TDD quality gates
const implementation = await tddConvergence({
...inputs,
plan: plan.tasks,
targetQuality: 90
}, ctx);
// Verify with GSD
const verification = await executePhase({
...inputs,
tasks: implementation.artifacts
}, ctx);
return { plan, implementation, verification };
}
Modifying Process Parameters
Most processes accept configuration through inputs:
{
"feature": "User authentication",
"targetQuality": 95,
"maxIterations": 10,
"requirements": [
"Support OAuth2",
"Include MFA"
],
"constraints": [
"Must use existing user table",
"No breaking API changes"
]
}
Best Practices
Choosing the Right Process
- Match your domain: Start with the specialization that matches your work
- Check the methodology: Consider which methodology fits your project style
- Review inputs carefully: Understand what configuration options are available
- Read the examples: Look at example inputs in the
examples/directories underlibrary/
Customization Tips
- Start simple: Use processes as-is before customizing
- Layer changes: Extend rather than modify base processes
- Preserve breakpoints: Keep human approval gates in critical paths
- Test incrementally: Validate customizations with small inputs first
Quality Considerations
- Use quality convergence: Processes with quality scoring help ensure high standards
- Enable breakpoints: Human review catches issues early
- Compose methodologies: Combine TDD with your domain process for better results
- Track iterations: Monitor how many iterations processes require
See Also
- Process Definitions - How to create your own processes
- Quality Convergence - Quality gates and scoring
- Breakpoints - Human-in-the-loop approval
- Parallel Execution - Running tasks concurrently