oc-orchestrator

Topics in the source

• Orchestrator
• /oc-ops — Command Reference
• Session-Start Protocol
• Architecture
• Design Constraints
• Project Registry
• Persistence Model
• Registry Schema (stored in skillstate.registry of the tracked checkpoint)

On first invocation, read references/orchestrator.md and follow its welcome protocol. Pipeline coordinator for the opchain dev ecosystem. This skill does NOT build, audit, deploy, or design — it reads every other skill's checkpoints, maintains a project registry, and answers three questions: 1. Where am I? — Cross-skill status across all registered projects. 2. What's next? — The single highest-priority action based on pipeline position. 3. Route me. — Smart dispatch to the right skill based on intent. This is an additive layer. Every existing skill retains its own welcome protocol and works independently. The oc-orchestrator provides a better front door and a unified view across projects — it doesn't replace any skill's internal logic. -- What's wired vs. what's a pattern. The oc-orchestrator is a reasoning skill — most "commands" are behaviors Claude performs by reading checkpoints and routing, not shell entry points. The pieces backed by real tooling are the checkpoint reads/writes: node scripts/checkpoint.mjs status | next | doctor | validate | update | done | init. /oc-ops status, /oc-ops next, and /oc-ops blockers lean on those directly. /oc-ops register, /oc-ops switch, /oc-

This is an excerpt. Refer to the complete source and its current requirements.