agent-builder/scripts/templates/domains

Domain Templates

Pre-built pipeline templates for common use cases. The builder agent reads these during /agent-factory:build Phase 0 to pre-populate the design sketch.

Available Templates

Template	Domain	Agents	Pipeline
content-pipeline	Content production	content-researcher, content-writer, content-reviewer	Research → Draft → Review → Publish
code-review	Code review	code-analyzer, review-writer, standards-checker	Analyze → Write review → Check standards → Post
monitoring	System monitoring	monitor-checker, incident-reporter, remediation-advisor	Check → Detect → Report → Advise
research-synthesis	Research & analysis	source-gatherer, synthesizer, fact-checker	Gather → Synthesize → Verify → Produce brief
data-processing	Data transformation	data-validator, transformer, quality-checker	Validate → Transform → Check quality → Save
customer-support	Customer support	ticket-classifier, response-drafter, escalation-checker	Classify → Draft → Escalation check → Route
devops-automation	DevOps automation	deploy-checker, incident-detector, runbook-executor	Deploy check → Detect → Execute runbook → Report
legal-review	Legal document review	clause-extractor, risk-assessor, compliance-checker	Extract → Assess risk → Compliance check → Report
sales-intelligence	Sales intelligence	prospect-researcher, pitch-customizer, follow-up-tracker	Research → Customize pitch → Track follow-up → Report
security-audit	Security auditing	config-scanner, vulnerability-checker, remediation-advisor	Scan config → Check CVEs → Remediation → Report

Usage

During /agent-factory:build, choose a template when prompted: "Would you like to start from a domain template?"

The builder reads the chosen template and pre-populates:

• Agent roles and descriptions
• Pipeline steps and handoff points
• Recommended hooks for the domain
• Example CLAUDE.md sections

Template format

Each template is a plain markdown file with {{PLACEHOLDER}} variables. The builder agent replaces placeholders with project-specific values during scaffolding. All templates follow the same structure:

1. Header comment (domain description)
2. Agent definitions (frontmatter + system prompt per agent)
3. Pipeline skill template
4. Recommended hooks
5. Example CLAUDE.md sections

Placeholders

All templates use these standard placeholders:

Placeholder	Description
{{PROJECT_DIR}}	Absolute path to the user's project
{{AGENT_NAME}}	Name of the agent being generated
{{PIPELINE_NAME}}	Name of the pipeline skill
{{SCHEDULE}}	Cron expression or schedule description
{{DOMAIN}}	Domain name (e.g., "content", "code-review")

Creating custom templates

Copy any existing template and modify it. The builder agent can also generate custom templates during the build workflow.