status

Retrieve active Maestro session metadata, phase breakdowns, and token usage.

453|34|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/josstei/maestro-orchestrate --skill status-josstei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/josstei/maestro-orchestrate/tree/main/plugins/maestro/skills/status
Command: npx skills add https://github.com/josstei/maestro-orchestrate --skill status-josstei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When working with Maestro multi-agent development workflows, users need to audit active session progress, diagnose stalled or failed phases, and track resource usage without accidentally modifying the session state, which can introduce errors or disrupt ongoing work.

Core Features & Use Cases

  • Full Session Metadata Reporting: Retrieves and displays session ID, creation timestamp, active workflow mode, and overall session status.
  • Phase Breakdown: Shows completed phases with timestamps, the current active phase, pending upcoming phases, and failed phases with associated error summaries.
  • Resource & Change Tracking: Reports the full file manifest (created, modified, deleted files), token usage per specialist agent, and any unresolved errors in the session.
  • Use Case: If a Maestro development workflow stalls mid-execution, use this skill to quickly identify if a phase failed, which files were altered, and how many tokens each agent consumed, all without changing the session state.

Quick Start

Use the status skill to get a complete, non-mutating summary of your active Maestro session's progress, phase status, and resource usage.

Frequently Asked Questions about status

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

FAQPage Schema
How do I check Maestro session status without modifying the workflow state?

To check Maestro session status without modifying workflow state, retrieve session metadata, phase breakdowns, and resource usage read-only. This prevents unintended mutations to persistent session data while auditing active session progress and diagnosing stalled phases.

How do I track per-agent token usage in a multi-agent development workflow?

Track per-agent token usage in a multi-agent development workflow by retrieving active session state information. This surfaces token consumption metrics for each specialist agent, alongside the file change manifest, allowing you to audit resource consumption without disrupting ongoing work.

Why does my Maestro workflow stall mid-execution and how can I diagnose failed phases?

Diagnose a stalled Maestro workflow by retrieving a phase breakdown from persistent session state. This identifies failed phases with associated error summaries, shows the current active phase, and lists pending upcoming phases to pinpoint exactly where the multi-agent execution halted.

Can I audit file changes in a Maestro multi-agent session without disrupting active agents?

Yes, you can audit file changes in a Maestro session without disrupting active agents. A non-mutating status retrieval reports the full file manifest, including created, modified, and deleted files, directly from persistent session state without altering the ongoing workflow.

What is the best way to monitor dev orchestration progress across specialist agents?

The best way to monitor dev orchestration progress is retrieving a non-mutating session status summary. This provides a complete overview of session ID, active workflow mode, phase timestamps, and unresolved errors, enabling effective session monitoring across specialist agents without state changes.

Does retrieving Maestro session metadata require any specific dependencies or components?

Retrieving Maestro session metadata requires no specific external dependencies or components. It operates by directly querying persistent Maestro session state to extract session ID, creation timestamp, and overall session status without needing additional environment setup.