| name | zob-factory |
| description | Use when designing or running repeatable software factories with manifests, checkpoints, validators, sentinels, smoke/pilot/batch gates. |
ZOB Factory Skill
When to use
Use when the task is repeated, batchable, or should become a reusable system rather than a one-off feature.
Workflow
- Spec first: define input manifest, outputs, validators, and no-ship rules.
- Factory design: deterministic scaffolding first, LLM enrichment second.
- Smoke: one item only.
- Oracle: require validation evidence before pilot/batch.
- Pilot: 10 items max with bounded concurrency.
- Batch: only after pilot sentinel and oracle gate.
Agent Factory shape
Some factories produce not only code or reports, but a supervised team workflow. Treat these as Agent Factories. A safe Agent Factory defines:
- ZAgent roles, prompts, default modes, and allowed authority;
- ZTeam topology, aliases, rooms, entry agent, and
parentVisible communication policy;
- optional Scoped ZTeam Mode Pack under
.pi/zteams/ with schema zob.zteam-modes.v1, canonical base modes only, localOnly true, networkEnabled false, bodyStored false, and no defaults unless strictly aligned/narrowing-only;
- Team Contract Pack metadata: parent-visible coordination, hidden peer chat disabled, local-only transport, body-free durable records, manual launch, spawn-count=0, and owner/oracle no-ship gates;
- optional manual tmux launcher with start/attach/status/close only;
- startup kickoff templates or rendered kickoff files passed as
pi @kickoff.md;
- run artifacts such as
run-manifest.json, workgraph/status/iteration logs, readiness or kickoff-dispatch records;
- validation and oracle/no-ship gates before completion claims.
Do not treat launching a tmux team, printing /zteam launch-plan, or receiving ZPeer ACKs as factory success. Success comes from evidence artifacts, validators, and oracle review.
Required artifacts
manifest.jsonagentic-plan.jsoncheckpoints/outputs/validation.json- phase sentinel (
SMOKE_PASSED.sentinel, PILOT_PASSED.sentinel, or BATCH_PASSED.sentinel)
DONE.sentinel only after validation passes
For Agent Factories, also prefer:
- team manifest or generated run-scoped team manifest
- kickoff templates or rendered startup kickoff files
autonomous-workgraph.md / autonomous-status.md / iteration-log.mdkickoff-dispatch.json or equivalent body-free startup proof- communication protocol, Scoped ZTeam Mode Pack/Team Contract Pack posture when used, and no-ship policy
