dispatch

Enforce a pinned 7-axis wire-format contract for orchestrator-to-worker handoffs.

8|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/usurobor/cnos --skill dispatch-usurobor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dispatch
Source: https://github.com/usurobor/cnos/tree/main/src/packages/cnos.handoff/skills/handoff/dispatch
Command: npx skills add https://github.com/usurobor/cnos --skill dispatch-usurobor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dispatch-time prompts often drift or leak internal reasoning when moving work between γ (orchestrator) and α/β (workers). This Skill provides a formal, pinned wire-format contract to guide every handoff.

Core Features & Use Cases

  • Pin the 7-axis implementation contract and route through δ before α begins work.
  • Enforce a four-surface handshake: γ template, δ inward enrichment, α constraint, and β verification.
  • Support mid-flight re-pinning with gamma-clarification logging to preserve auditable history.
  • Use when coordinating cycles that require exact language, packaging, and runtime assumptions.

Quick Start

Create a dispatch prompt that carries the cycle issue reference, the branch, the Tier-3 skills, and a fully pinned 7-axis implementation contract, then route it through δ before α starts work.

Frequently Asked Questions about dispatch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent internal reasoning from leaking during orchestrator-to-worker handoffs?

When orchestrator-to-worker handoffs leak internal reasoning, you need a wire-format envelope to move cycle work securely. This dispatch mechanism pins implementation axes and routes through an inward enrichment surface before workers begin execution.

What is a pinned implementation contract for role-to-role dispatch?

A pinned implementation contract for role-to-role dispatch is a formal wire-format that establishes a four-surface handshake. It ensures orchestrator templates, inward enrichment, worker constraints, and verification surfaces are enforced before and during cycle execution.

How do I pin the 7-axis implementation contract before starting worker cycles?

To pin the 7-axis implementation contract before starting worker cycles, create a dispatch prompt carrying the cycle issue reference, branch, and Tier-3 skills. Route this prompt through an inward enrichment surface to ensure all axes are fully pinned.

Can I re-pin an implementation contract mid-flight if a cycle axis remains unpinned?

Yes, you can re-pin an implementation contract mid-flight when a cycle axis remains unpinned. The dispatch pathway supports mid-flight re-pinning with clarification logging, preserving an auditable history of changes during the active cycle.

When do I need a formal wire-format envelope for prompt handoffs?

You need a formal wire-format envelope for prompt handoffs when coordinating cycles that require exact language, packaging, and runtime assumptions. It is essential for governance surfaces where orchestrator-to-worker handoffs must maintain strict implementation axis enforcement.