Track Project Conductor Status and Progress

Conductor Status displays the current status of a Conductor project - overall progress, active tracks, and next actions - after verifying Conductor is initialized (product.md and tracks.md exist) and that at least one track has been registered.

It collects project name/description from product.md, a tracks overview (total/completed/in-progress/pending) from tracks.md, and for each track a detailed analysis: task counts by status parsed from plan.md, the current phase (the first phase with an incomplete task) and next pending task, metadata (type, created/updated dates, status) from metadata.json, and any noted blockers or dependencies from spec.md. Blocker detection specifically scans for tasks marked BLOCKED:, dependencies on incomplete tracks, and failed verification tasks. With no argument it renders a full project status: overall track/task progress with a text progress bar, a track-summary table, the currently active track's phase and task breakdown, a numbered next-actions list, and any blockers found. Given a track ID it renders that track's detail instead: its specification summary and acceptance-criteria checklist, a phase-by-phase task breakdown with the current task marked, related git commits, and its own next-steps list.

Two alternate output modes exist for automation: --quick/-q prints a single-line summary (project name, overall task fraction/percentage, active track and task), and --json emits a structured object with track/task counts, the current track/phase/task, and a blockers array. Named error states cover Conductor not being initialized (points to /conductor:setup), no tracks yet created (points to /conductor:new-track), and an unrecognized track ID (lists the available tracks instead).

Use it to check a Conductor project's overall progress, see what's currently being worked on, or get a single track's detailed status and blockers - as a read-only reporting skill, not one that changes any track state. For actually executing a track's plan, that's the separate /conductor:implement skill; this one only reports.

Input is an optional track ID and an optional --quick or --json flag. Output is a formatted status report (full project, single track, one-line quick summary, or JSON), always readable directly from conductor/'s own tracked files rather than a separate state store.

It reads the local conductor/ directory structure (product.md, tracks.md, per-track plan.md/metadata.json/spec.md) and correlates git commit history for a single track's report.

Developers and teams using the Conductor workflow system who want a quick, accurate progress report - overall or per-track - including blockers and next steps, in human-readable or machine-readable (JSON) form.