Six common shapes for the specialists master can spawn. Each one is a
starting point, not a fixed identity — fork the template, give it your
voice, register it in block3.yaml, then assign it work.
Owns the deploy chain, the audit trail, and the rollback path.
Owns
deployment scripts · CI/CD pipelines · environment configs · release notes · rollback playbook
Tools
shell scripts
MCP · cloud
git hooks
CI triggers
Typical skills
/deploy
/audit
/rollback
/status
/hotfix
Spawn as soon as the project has something to ship — even a single
staging environment is enough. The audit trail is more useful early
than late.
Keeps the documentation aligned with the code, not behind it.
Owns
README files · architecture notes · API references · in-repo guides · HTML artifacts
Tools
file watch
git diff parsers
doc generators
MCP · search
Typical skills
/refresh-readme
/build-api-docs
/audit-stale
/publish-changelog
Spawn when the project has more moving parts than the operator can hold
in their head. The agent's job is to keep the answer to "where is X
documented?" always one click away.
Owns the data layer end-to-end — from raw input to validated snapshot.
Owns
ingest pipelines · validation rules · snapshots · universe management · ETL
Tools
shell scripts
MCP · storage
MCP · DB
scheduled jobs
Typical skills
/ingest
/validate
/snapshot
/rebuild-universe
/diff-versions
Spawn the moment raw data starts arriving and someone has to take care
of it — schemas, freshness, drift. Decoupling data ownership from
analysis avoids the classic "the notebook broke because the schema
changed" trap.
Runs systematic exploration on top of curated data.
Owns
analysis artifacts · hypothesis logs · model evaluations · methodology notes
Tools
Python / R harness
MCP · search
notebook tooling
citation hooks
Typical skills
/investigate
/evaluate
/propose-hypothesis
/summarize-findings
Spawn when the data agent has produced something worth reasoning about.
Research lives downstream of data: it never owns the pipeline, only
the questions and the answers.
Per-project networking, runtime, and security surface.
Owns
reverse proxy config · DNS records (project-scoped) · secrets · runtime envs · container or VM config
Tools
shell scripts
MCP · DNS
MCP · secrets
restart triggers
Typical skills
/configure-proxy
/rotate-secret
/audit-network
/restart-service
Spawn when the project goes from local-only to having a public surface.
Distinct from the Holding tier: infra here is project-scoped, while
Holding manages networking across many projects on the same VM.
Reads code and findings critically before they ship.
Owns
review checklists · regression suites · smoke tests · review reports · convention rules
Tools
test runners
static analysis
git hooks
MCP · linters
Typical skills
/review-pr
/run-regression
/smoke-test
/audit-changes
Spawn when more than one agent is contributing to the same files and
consistency starts slipping. A second pair of eyes that never gets
tired and writes its findings down.