orchestrator-status

Inspect orchestrator configuration, change statuses, and loaded skills from CLAUDE.md.

Updated Aug 23, 2026

Search Tags:#registry #sdd #status #orchestrator #openspec #changes

Ready to run

npx skills add https://github.com/fearovex/agent-config --skill orchestrator-status-fearovex

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: orchestrator-status
Source: https://github.com/fearovex/agent-config/tree/main/skills/orchestrator-status
Command: npx skills add https://github.com/fearovex/agent-config --skill orchestrator-status-fearovex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly introspect the current state of the SDD Orchestrator, including active changes, loaded skills, and the configuration source, without mutating any files or running changes.

Core Features & Use Cases

Reads the CLAUDE.md to determine whether intent classification is enabled.
Scans openspec/changes for active work and reports per-change status and artifacts.
Enumerates loaded skills from CLAUDE.md's Skills Registry and highlights core vs phase skills.
Useful for on-demand health checks, status dashboards, and pre-change validations.

Quick Start

Run the orchestrator-status check to retrieve a live snapshot of the orchestrator state.

Frequently Asked Questions about orchestrator-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check the current orchestrator state in OpenSpec?▼

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.

How do I list active changes and their artifacts in openspec/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.

How can I extract the Skills Registry from CLAUDE.md to see loaded orchestrator skills?▼

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.

Does checking orchestrator status modify any project files?▼

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.

What do I need to use orchestrator-status for health checks?▼

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.