Menu
Use when designing or running repeatable software factories with manifests, checkpoints, validators, sentinels, smoke/pilot/batch gates.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use when reviewing or modifying ZOB communication, ledgers, Mission Control coms, or live transport safety gates.
Use when an active ZOB handoff, live peer question, required-local coms delivery, or orchestration message is needed.
Use when planning, using, reviewing, or implementing ZOB /goal-linked TODOs, subtodos, TODO HUD progress, delegated TODO claims, or hierarchical subagent work graphs.
Use when working inside the ZOB Pi harness, designing agentic workflows, creating specialist prompts, adding Pi extensions, or turning repeated tasks into software factories.
Use before non-trivial work, uncertain tool selection, orchestration, delegation, context lookup, factory work, autonomous-runtime claims, or evidence-gated completion.
Use when driving the append-only metadata-only worklist blackboard — appending events, reading derived directives, leasing/satisfying directives by content hash, delivering idempotent DIRECTIVE_READY notifications, running the liveness watchdog (observe/escalate), or building/querying the dependency DAG.
| name | zob-factory |
| description | Use when designing or running repeatable software factories with manifests, checkpoints, validators, sentinels, smoke/pilot/batch gates. |
Use when the task is repeated, batchable, or should become a reusable system rather than a one-off feature.
Some factories produce not only code or reports, but a supervised team workflow. Treat these as Agent Factories. A safe Agent Factory defines:
parentVisible communication policy;.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;pi @kickoff.md;run-manifest.json, workgraph/status/iteration logs, readiness or kickoff-dispatch records;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.
manifest.jsonagentic-plan.jsoncheckpoints/outputs/validation.jsonSMOKE_PASSED.sentinel, PILOT_PASSED.sentinel, or BATCH_PASSED.sentinel)DONE.sentinel only after validation passesFor Agent Factories, also prefer:
autonomous-workgraph.md / autonomous-status.md / iteration-log.mdkickoff-dispatch.json or equivalent body-free startup proof