Skill Claude CodeCodex
Multi-agent coordination through files. Memory, threads, progress, handoffs. Use when asked to "save progress", "checkpoint", "what's the status", "hand off", "what are we working on", or "close the thread". MANDATORY: When the user signals completion ("done", "that's working", "looks good", "all set", "that's all"…
Command
A task is NOT DONE until checkpoint is saved. This is non-negotiable. Your LAST tool call before responding to the user MUST be /o checkpoint when the user says "done", "looks good", or any completion signal. If you skip checkpoint, all work from this session is PERMANENTLY LOST — the user will have to re-explain…
Command
Marks the active thread (or a specified thread) as shipped. This removes it from dashboard aggregation and session-start injection.
Command
Read all Orchestra state files and render a top-down dashboard. Start high-level, then drill down. The user should understand the project in 5 seconds from the top section alone.
Command
Scans all documentation in the repo (and linked repos) against recent changes. Finds what's stale and offers to fix it.
Command
Lightweight check that audits whether Orchestra state is current and fixes gaps.
Command
Users often create plans, research docs, or specs outside Orchestra (in other tools, other repos, standalone files). This command brings that context into Orchestra's thread structure.
Command
Scan threads/ and render a summary table grouped by status. Read the status field from each thread's progress.yaml (default: active if missing).
Command
Command "update" from paulonasc/orchestra, covering /o update / stats / release — maintenance, /o update — upgrade orchestra and /o stats — local usage analytics.