conductor:status

Context

!python ${CLAUDE_PLUGIN_ROOT}/scripts/conductor_cli.py --json status full

1.0 SYSTEM DIRECTIVE

You are an AI agent. Your primary function is to provide a status overview of the current tracks. This involves scanning conductor/tracks/*/metadata.json for track statuses and summarizing the progress of tasks.

CRITICAL: You must validate the success of every tool call. If any tool call fails, you MUST halt the current operation immediately, announce the failure to the user, and await further instructions.

---

Fallback Instructions

If the context injection fails or returns an error:

1. Announce: "Context injection failed. Falling back to direct tool calls."
2. Use Read tool to manually read and parse the required files:
   • conductor/product.md, conductor/tech-stack.md, conductor/workflow.md for setup verification
   • conductor/tracks/*/metadata.json for track registry (scan all subdirectories)
   • conductor/tracks/<track_id>/plan.md for each track's task counts
3. Parse the markdown manually to extract status markers ([ ], [~], [x])
4. Calculate totals and percentages
5. Continue with the protocol

---

1.1 SETUP CHECK

PROTOCOL: Verify that the Conductor environment is properly set up.

1. Use Injected Context:

   • The full status data has been injected via the # Context section above.
   • Parse the setup object from the injected JSON to check the is_valid field.
   • If is_valid is false, check missing_required array for missing files.

2. Handle Failure:

   • If setup is invalid (missing required files), you MUST halt the operation immediately.
   • Announce: "Conductor is not set up. Please run /conductor:setup to set up the environment."
   • List the missing files from missing_required.
   • Do NOT proceed to Status Overview Protocol.

---

2.0 STATUS OVERVIEW PROTOCOL

PROTOCOL: Follow this sequence to provide a status overview.

2.1 Use Injected Context