Workers
Worker Types
| Type | Purpose |
|---|---|
| CodeWorker | Implements features, fixes bugs, refactors |
| ContentWorker | Drafts content, maintains voice consistency |
| ResearchWorker | Analysis, market research, competitive intel |
| OpsWorker | Reports, monitoring, automation |
| PersonaWorker | A worker that runs as a chat bot, such as the Setup bot |
| Library | Shared utilities (not directly executable) |
HQ ships 43 workers in core/workers/public/. The full list, with each worker’s type and description, is core/workers/registry.yaml. HQ regenerates that file from each worker.yaml, so don’t edit it by hand.
Dev Team (18 Workers)
A development team at core/workers/public/dev-team/.
| Worker | Type | Skills |
|---|---|---|
| project-manager | OpsWorker | PRD lifecycle, issue selection, learning aggregation |
| task-executor | OpsWorker | Analyze issues, route to workers, validate completion |
| pipeline-conductor | OpsWorker | Routing rules for /run-project --pipeline |
| architect | CodeWorker | System design, API design, architecture decisions |
| backend-dev | CodeWorker | API endpoints, business logic, backend implementation |
| frontend-dev | CodeWorker | React/Next components, pages, UI implementation |
| database-dev | CodeWorker | Schema design, migrations, query optimization |
| infra-dev | CodeWorker | CI/CD pipelines, deployment configurations, monitoring setup |
| dev-qa-tester | CodeWorker | Testing, browser automation, accessibility, demo accounts |
| code-reviewer | CodeWorker | PR review, merge management, code quality gating |
| reality-checker | CodeWorker | Final quality gate that cross-validates QA findings |
| codex-coder | CodeWorker | Code generation through the OpenAI Codex SDK |
| codex-debugger | CodeWorker | Debugging and root-cause analysis through the OpenAI Codex SDK |
| codex-reviewer | CodeWorker | Second-opinion code review through the OpenAI Codex SDK |
| context-manager | CodeWorker | Discover, maintain, and audit project context |
| motion-designer | CodeWorker | Animations, transitions, visual polish, image generation |
| knowledge-curator | CodeWorker | Process learnings, update knowledge bases, maintain documentation |
| product-planner | CodeWorker | PRD creation, technical specs, API contracts |
Content Team
Multi-perspective content review at core/workers/public/content-*/.
| Worker | Focus | Skills |
|---|---|---|
| content-brand | Voice & tone | Voice analysis, tone check, messaging alignment |
| content-sales | Conversion | Conversion copy, CTAs, value props |
| content-product | Accuracy | Feature accuracy, technical claims verification |
| content-legal | Compliance | Regulatory compliance, claim verification |
| content-shared | Shared code | TypeScript library for analysis, scoring, and reporting. It has no worker.yaml, so it is not in the registry or the count of 43 |
Other Teams
| Team | Workers | Path |
|---|---|---|
| Social | social-strategist, social-reviewer, social-publisher, social-verifier, social-shared | core/workers/public/social-*/ |
| Gardener | garden-scout, garden-auditor, garden-curator | core/workers/public/gardener-team/ |
Standalone Workers
| Worker | Purpose |
|---|---|
| setup | The Setup bot that gets a new HQ working |
| security-scanner | Security scanning and vulnerability detection |
| accessibility-auditor | WCAG 2.2 AA auditing |
| qa-tester | Adversarial website testing with screenshot evidence |
| performance-benchmarker | Core Web Vitals, load testing, capacity planning |
| exec-summary | Executive summaries with strict word limits |
| frontend-designer | UI generation |
| paper-designer | Paper Desktop design bridge |
| site-builder | Build and deploy local business websites from a template and config |
| ontology | Maintains a company’s ontology and signals |
| knowledge-tagger | Classifies knowledge docs against the ontology |
| pretty-mermaid | Mermaid diagram rendering |
| ascii-artist | ASCII banner images for social posts and OG images |
Worker YAML Schema
Every worker is defined by a worker.yaml:
worker: id: my-worker name: My Worker type: CodeWorker version: "1.0"
execution: mode: on_demand # most bundled workers use on_demand; the template uses on-demand max_runtime: 30m
context: base: - core/knowledge/public/Ralph/ # Knowledge to load dynamic: [] exclude: []
verification: post_execute: - check: typescript command: npm run typecheck approval_required: false
tasks: source: companies/my-company/projects/my-project/prd.json
output: destination: workspace/reports/ format: markdown
instructions: | Multi-line instructions for the worker...Creating Custom Workers
Use /newworker to scaffold:
/newworkerThe wizard asks for:
- Worker ID and name
- Type (CodeWorker, ContentWorker, etc.)
- Skills (name + description for each)
- Knowledge context paths
- Execution rules
It then asks whether the worker belongs to one company or ships with HQ, and generates it at companies/{co}/workers/{id}/ or core/workers/public/{id}/. The default is company scope. Choose core/ only for a worker meant to ship with HQ releases: /update-hq replaces core/, so a worker you add there for yourself is lost on the next update. The generated folder:
{id}/├── worker.yaml├── skills/│ ├── skill-one.md│ └── skill-two.md└── README.md