orchestrator-status

To check the orchestrator state, run a status check to retrieve a live snapshot of active changes, loaded skills, and configuration source. This process reads CLAUDE.md and scans openspec/changes without mutating any files or running changes.

Listing active changes involves scanning non-archived directories under openspec/changes and classifying each by status: verified, in-progress, designing, proposed, or unknown. The status check also notes the specific artifacts contained within each change directory.

Extracting the Skills Registry from CLAUDE.md enumerates loaded orchestrator skills, highlighting core and phase categories. It reports the total count of skills, providing a comprehensive view of what the orchestrator currently has loaded.

Checking orchestrator status does not modify any files. The process performs a read-only introspection of the current state, including active changes and loaded skills, making it safe for on-demand health checks and pre-change validations.

Using orchestrator-status for health checks requires a CLAUDE.md file containing the Skills Registry and an openspec/changes directory. It reads these configurations to provide a live snapshot of the orchestrator state without requiring additional dependencies.