R76.H5 — Packet: colibri-sigma-orchestrator skill stub

Execution plan (line-by-line word budget)

The target skill file is ≤ 200 lines. Breakdown:

Block	Section	Lines	Rationale
1	YAML frontmatter	~7	Frontmatter fence + 4 keys + fence.
2	H1 + identity banner	~8	Title + blockquote (greek/tier/contract/phase-0).
3	When to invoke	~10	5 bullet triggers + short intro line.
4	Phase A — Plan	~25	Intro + 8-step numbered list + manifest template pointer.
5	Phase W — Waves	~18	Intro + gate-check bullets + gate-fail rule.
6	Phase B — Seal	~22	Intro + 8-step seal sequence + failure modes pointer.
7	Non-negotiables	~12	6 rules (one line each) + intro line.
8	Phase 0 reality stamp	~14	Dense paragraph + bullets on agent runtime defer.
9	Example usage	~16	Walkthrough of “open round R76” case.
10	Integration with other skills	~8	4-bullet peer-skill list.
11	References	~8	CLAUDE.md pointers + contract + spawn artifact + ADR.
	Blank-line padding	~20	Blank lines between sections.
Total		~168	Within 200-line budget.

Step 4 action plan

4.1 Create directories

Two new directories (both must be created; neither exists):

• .agents/skills/colibri-sigma-orchestrator/ (canon)
• .claude/skills/colibri-sigma-orchestrator/ (mirror)

Directories auto-create when Write is called on a nested path — no explicit mkdir required.

4.2 Write canon

.agents/skills/colibri-sigma-orchestrator/SKILL.md — full contents per contract §Body sections.

4.3 Sync to mirror

After canon is written, replicate byte-identical to .claude/skills/colibri-sigma-orchestrator/SKILL.md. Use cp in bash:

cp .agents/skills/colibri-sigma-orchestrator/SKILL.md .claude/skills/colibri-sigma-orchestrator/SKILL.md

Since cp will fail if destination directory doesn’t exist on some platforms, use mkdir -p first (Windows Git Bash handles -p):

mkdir -p .claude/skills/colibri-sigma-orchestrator
cp .agents/skills/colibri-sigma-orchestrator/SKILL.md .claude/skills/colibri-sigma-orchestrator/SKILL.md

4.4 Verify YAML safely

After write, head -20 canon and confirm the YAML fence is correct and description: is surrounded by double quotes (not broken mid-value by an unquoted colon).

Step 5 verification plan

1. ls both paths to confirm files exist.
2. diff the two files — must return zero (byte-identical).
3. Line count both: wc -l. Target canon ≤ 200.
4. head -20 canon to sanity-check YAML frontmatter.
5. Run full gate triplet from worktree root: npm run build && npm run lint && npm test.

Expected test result: 1084 / 1084 passing per R75 Wave I baseline. The skill file touches neither src/ nor Jest config, so a regression would indicate a cascading issue elsewhere and must be investigated. Known pre-existing smoke flake is documented and not a regression.

YAML hazard check

The description string contains these colon-containing substrings:

• Colibri Sigma Orchestrator (T1) contract-reference skill — Phase A (plan manifest) → Phase W (watch waves) → Phase B (seal).
• Greek: α (alpha) — System Core + round choreography.
• No executable tool dispatch in Phase 0 — agent runtime deferred to Phase 1.5 per ADR-005.
• Contract: docs/agents/sigma-orchestrator.md.

Without surrounding double quotes, gray-matter would try to parse Greek: α as a new key, failing. Double-quoting the full string neutralizes all colons.

Commit plan

Single commit on feature/r76-h5-sigma-skill:

feat(r76-h5): create colibri-sigma-orchestrator skill stub

Files staged:

• .agents/skills/colibri-sigma-orchestrator/SKILL.md (canon)
• .claude/skills/colibri-sigma-orchestrator/SKILL.md (mirror)
• docs/audits/r76-h5-sigma-skill-audit.md
• docs/contracts/r76-h5-sigma-skill-contract.md
• docs/packets/r76-h5-sigma-skill-packet.md
• docs/verification/r76-h5-sigma-skill-verification.md

PR plan

• Branch: feature/r76-h5-sigma-skill
• Title: R76.H5: create colibri-sigma-orchestrator skill stub (contract-reference)
• Body: per task prompt template, with writeback block queued (no live MCP client).

Risks

• Windows cp: Git Bash on Windows handles cp and mkdir -p — previously verified in Wave E / F / G / H chores.
• .claude/settings.local.json persistent drift (memory-tracked): do not stage it.
• Rate-limit risk: single executor, no parallel sub-agents — no issue.
• Line count budget: conservative per table above (~168 lines with padding).