conductor-status

To get a project progress overview for multi-track Conductor projects, run /conductor-status. It reads the Tracks Registry and implementation plans to summarize completed, in-progress, and pending tasks across all tracks.

The best way to track project phases and identify blockers across multiple platforms is to parse the Tracks Registry. This approach aggregates task statuses and surfaces blockers to keep stakeholders aligned.

Status tracking for Conductor implementation plans works by parsing the plan, counting phases and tasks, identifying the current in-progress task, the next pending task, and reporting total phases, total tasks, and overall progress.

Yes, you can use conductor-status to view the next pending task. It reads the Tracks Registry to identify both the current in-progress task and the next pending task, summarizing them in a concise overview.

Project status tracking with conductor-status requires no specific dependencies or components. It functions independently by reading the Tracks Registry and tracks implementations to produce a concise project progress overview.

Your project progress overview shows incomplete task counts because the system parses the implementation plan to distinguish completed, in-progress, and pending tasks. It aggregates these statuses to report total tasks and overall progress accurately.