R76.H5 — Contract: colibri-sigma-orchestrator skill stub
Behavioral contract
The colibri-sigma-orchestrator skill is a contract-reference skill — it points at the authoritative docs/agents/sigma-orchestrator.md and does not attempt to duplicate or paraphrase its full content. It tells the reader where to find the Sigma role, when to invoke it, and the shape of each phase, then hands off to the contract for details.
File structure
Canon file
- Path:
.agents/skills/colibri-sigma-orchestrator/SKILL.md - Encoding: UTF-8, LF line endings (match repo convention).
- Line budget: ≤ 200 lines total (including frontmatter + body).
Mirror file
- Path:
.claude/skills/colibri-sigma-orchestrator/SKILL.md - Property: byte-identical to canon on creation.
- Sync rule: canon is source of truth; future edits go through canon and then resync (per CLAUDE.md §9.2).
YAML frontmatter
Exactly these keys, in this order:
---
name: colibri-sigma-orchestrator
description: "<quoted single-line description, contains multiple colons>"
round: R76
updated: 2026-04-18
---
Required properties of description:
- Double-quoted whole string (colons inside would break YAML parsing otherwise — memory-tracked hazard).
- Names the role:
Colibri Sigma Orchestrator (T1). - Names the classification:
contract-reference skill. - Summarizes three phases:
Phase A (plan) -> Phase W (watch) -> Phase B (seal). - States activity scope:
Sigma plans rounds, dispatches PM, gates waves, seals rounds. - States boundary:
Sigma does NOT write code. - States trigger conditions:
Use when the user opens a round, requests a Phase A plan, requests wave gate review, or requests round seal. - Names Greek letter:
Greek: alpha — System Core + round choreography. - Names the Phase 0 reality:
No executable tool dispatch in Phase 0 — agent runtime deferred to Phase 1.5 per ADR-005. - Names the contract path:
Contract: docs/agents/sigma-orchestrator.md.
Body sections (in order)
Section 1 — H1 + identity banner
- H1:
# Colibri Sigma Orchestrator Skill — Phase 0. - Blockquote with Greek letter (α), tier (T1), contract path, and Phase 0 reality (agent runtime Phase 1.5+).
- One-sentence identity: “Sigma plans rounds, dispatches PM, gates waves, and seals rounds; it does NOT write implementation code.”
Section 2 — When to invoke
Trigger list (bullets):
- User opens a new round (e.g. “open round R77”, “start R77”).
- User requests Phase A plan / manifest / round planning.
- User requests wave gate verification.
- User requests Phase B seal (audit_verify_chain + merkle_finalize).
- User asks “am I Sigma?” — answer per CLAUDE.md §2 hierarchy.
Section 3 — Phase A — Plan
Reference docs/agents/sigma-orchestrator.md §2 as the authority. Provide a compressed 8-step summary (from the contract’s step list) as a numbered list:
- Read previous round’s seal entry.
- Read open ADRs.
- Read human-supplied intent.
- Identify slices.
- Assign slices to waves.
- Write
.agents/spawns/rNN-<theme>/manifest.md. - Optional: write
_vault/rounds/rNN-<theme>/summary.md. - Record Phase A
thought_record(thought_type="plan").
Point readers to the contract’s manifest template + the live example at .agents/spawns/r76-phase-0-to-1-bridge/manifest.md.
Section 4 — Phase W — Waves
Reference docs/agents/sigma-orchestrator.md §3 as the authority. Summarize in one paragraph + bullet list:
- Sigma watches; PM dispatches.
- At each wave gate, verify: every task has
status=doneor justifiedcancelled, every task has athought_record, wave-level reflection from PM exists,audit_verify_chaingreen (for proof-grade work). - On gate approval, run
thought_record(thought_type="gate"). - On gate failure, pause the round and escalate to T0; never skip a gate.
Section 5 — Phase B — Seal
Reference docs/agents/sigma-orchestrator.md §4 as the authority. Provide the seal sequence in order:
audit_verify_chainacross every task in the round.- (Proof-grade)
merkle_finalize+merkle_root. - Update
docs/session-seal-sN.md. - Update
docs/roadmap/if plan shifted. - Create round commit on
feature/rNN-<theme>. - Final
thought_record(thought_type="reflection")— MUST precedemerkle_finalizeper CLAUDE.md §7. - Request T0 merge.
- On merge:
colibri-docs-sync+git worktree remove.
Section 6 — Non-negotiables
Copy the 6 rules verbatim from docs/agents/sigma-orchestrator.md §9:
- Sigma does not write code. Ever.
- Every phase produces a
thought_record. - No wave gate skipped.
- Final
thought_recordbeforemerkle_finalize. - Merging is T0 only.
- One round at a time.
Section 7 — Phase 0 reality stamp
Explicit statement that:
- Sigma is an active role (the R76 manifest is live proof).
- Sigma is NOT backed by an MCP tool runtime.
- Tools Sigma “runs” (
audit_verify_chain,merkle_finalize,merkle_root,thought_record,task_update) are manual invocations of the 14-tool Phase 0 MCP surface via an attached client. - Without a live MCP client, writeback is queued to PR bodies + memory per Wave H+I precedent.
- Full agent runtime is deferred to Phase 1.5 per ADR-005.
Section 8 — Example usage
One concrete invocation walkthrough, using the “open round R76” case (which happens to be live in the repo):
- User says: “open round R76 on the Phase 0 to 1 bridge theme”.
- Sigma runs steps 1–8 from Section 3.
- Output:
.agents/spawns/r76-phase-0-to-1-bridge/manifest.md(already exists since PR #152). - Sigma records Phase A
thought_recordvia MCP client if attached, else queues to round PR body. - Sigma awaits T0 authorization before entering Phase W.
Section 9 — References
Bullet list:
- CLAUDE.md §2, §3, §7
docs/agents/sigma-orchestrator.md(authoritative — 262 lines).agents/spawns/r76-phase-0-to-1-bridge/manifest.md(live Phase A example)docs/architecture/decisions/ADR-005-multi-model-defer.md§Decision- Sibling skills:
colibri-pm(T2),colibri-executor(T3),colibri-audit-proof(proof-grade)
Acceptance criteria
- Both files exist at canonical and mirror paths.
diffbetween canon + mirror returns empty.- YAML frontmatter parses via gray-matter (description double-quoted, colons safe).
- Total line count ≤ 200.
- No duplication of the full contract — only references + compressed summaries.
- No claims of executable Sigma tool dispatch in Phase 0.
npm run build && npm run lint && npm testall green.
Out of scope
- Rewriting
docs/agents/sigma-orchestrator.md. - Creating any Sigma MCP tools.
- Editing
src/,.github/workflows, or any other skill. - Editing vault mirror zone (
Obsidian Vault/Colibri/docs/).