zob-harness

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.

Use when running, documenting, or reviewing adaptive active search backend context discovery, including zob_context_search, optional ColGREP setup, and grep/find/read fallback behavior.

Use when designing or creating project-local ZAgent definitions or ZTeam bundles for full Pi-session agents tied to ZPeer, distinct from delegate subagents.

Use when designing or running repeatable software factories with manifests, checkpoints, validators, sentinels, smoke/pilot/batch gates.

Use when the user wants to analyze another agent harness such as Claude Code, Codex, Cursor, Aider, Pi/ZOB, existing skills/commands/prompts/sessions, and turn reliable patterns into reusable ZOB agent teams or factory proposals.

Use when the owner gives a plain-language intention and wants it rewritten into a safe, copy-pasteable ZOB parallel owner micro-worker pool drill or execution prompt.

Use when the owner gives a plain-language intention and wants the assistant to actively launch and operate a supervised ZOB parallel owner micro-worker pool workflow instead of only generating a prompt.

Use when launching, running, reviewing, or extending the Agentic Spec Team workflow that turns missions plus docs/data/mockups into evidence-first implementation specs.

Use when splitting a monolithic ZOB/Pi TypeScript extension into modules without behavior changes. Enforces split-only moves, export compatibility, local AGENTS.md context, and smoke validation.

Use when planning, reviewing, or executing governed ZOB commit/autocommit/autopush behavior through explicit /zcommit commands or the agent-executable zob_zcommit_run tool.

Use before delegating to ZOB specialist agents, choosing delegate_agent/delegate_task, selecting an agent, or deciding whether to set output_contract.

Use when enabling write-capable agents/factories safely through temp workspaces, diff gates, rollback metadata, and oracle review.

Use when adding or reviewing external adapters such as package metadata, GitHub, browser, cloud, or other APIs.

Use when running or reviewing zob_autonomous_* runtime tools, autonomous smoke/validation gates, or no-ship/global autonomy claims.

Use when reviewing, designing, triggering, or recovering from ZOB/Pi context compaction, branch summaries, long-goal continuation, or post-compaction skill/context reloads.

Use when selecting, previewing, validating, or implementing ZOB compute/effort profiles: auto, low, medium, high, xhigh, max.

Use when reading or controlling ZOB coms from Mission Control, including live presence, stale peers, command proposals, and oracle/no-ship review.

Use for skeptical validation, no-ship decisions, evidence gates, final reports, and regression/security reviews.

Use when turning a trusted reference project folder into ProjectDNA: a code-first knowledge graph, neutral sample-project plan, pointer capsules, and bounded cited context packs for future ZOB agents.

Use when turning product, feature, or factory ideas into testable ZOB specs and clarification gates before planning.