From maestro
Summarizes active Maestro session status including phase progress, file manifests, validation state, and unresolved errors without mutating state. Useful for read-only workflow checks.
How this skill is triggered — by the user, by Claude, or both
Slash command
/maestro:statusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Maestro MCP tools are registered with a namespace prefix in Claude Code. When instructions reference bare tool names, use the prefixed version:
Maestro MCP tools are registered with a namespace prefix in Claude Code. When instructions reference bare tool names, use the prefixed version:
| Referenced as | Actual tool name |
|---|---|
get_session_status | mcp__plugin_maestro_maestro__get_session_status |
resolve_settings | mcp__plugin_maestro_maestro__resolve_settings |
When instructions say "If X appears in your available tools, call it", search your available tools for the prefixed version.
Read ${CLAUDE_PLUGIN_ROOT}/references/architecture.md.
docs/maestro from MAESTRO_STATE_DIR.mcp__plugin_maestro_maestro__get_session_status to read the active session. If unavailable, read node ${CLAUDE_PLUGIN_ROOT}/scripts/read-active-session.js output or inspect docs/maestro/state/active-session.md directly via Read.npx claudepluginhub josstei/maestro-orchestrate --plugin maestroManages Maestro orchestration session state: creation, updates, tracking, resumption, and archiving via MCP tools, file edits, or scripts.