conductor-status
Conductor Status
Overview
This skill acts as a project dashboard. It aggregates information from the project's Tracks Registry and individual Implementation Plans to provide a unified view of what's done, what's currently being worked on, and what's coming up next.
When to Use
- When a user asks "What's the status?", "How are we doing?", or "Show me the project progress."
- To identify current blockers or the next actionable task.
Workflow
- Setup Check (Section 1.1): Using the Universal File Resolution Protocol, resolve and verify the existence of the Tracks Registry, Product Definition, Tech Stack, and Workflow. If ANY file is missing, halt immediately and announce that Conductor is not set up.
- Read Project Plan (Section 2.1): Read the Tracks Registry and each track's Implementation Plan. Support both
- [ ] **Track:(new) and## [ ] Track:(legacy) parsing formats. - Parse and Summarize (Section 2.2): Parse content to identify statuses (COMPLETED, IN PROGRESS, PENDING). Count total phases and tasks.
- Present Status Overview (Section 2.3): Generate a structured report including Current Date/Time, Project Status, Current Phase and Task, Next Action Needed, Blockers, Phases (total), Tasks (total), and Progress (tasks_completed/tasks_total, percentage).
Implementation Details
More from airclear/skills
bmad-tea
Enterprise Test Architecture (TEA) framework for quality engineering. Includes workflows for testing education (TEA Academy), risk-based test design, framework scaffolding, ATDD (Red-phase), CI/CD pipeline configuration, NFR (Non-functional) assessment, and quality auditing (0-100 scoring). Use for establishing or executing comprehensive testing strategies.
14conductor-setup
Scaffolds the project and sets up the Conductor environment for Context-Driven Development. Use when starting a new project or initializing the Conductor workflow in an existing (brownfield) project. This skill guides the user through project discovery, product definition, tech stack configuration, and initial track planning.
14conductor-implement
Executes the tasks defined in a specified track's plan. Use when the user wants to start or continue implementing a feature or bug fix. This skill manages the task lifecycle, adheres to the project's workflow, synchronizes project documentation upon completion, and offers track cleanup options.
11conductor-review
Acts as a Principal Software Engineer and Code Review Architect to review completed or in-progress work against project standards, style guides, and the implementation plan. Use when the user wants a quality check on their code or before finalizing a track.
10conductor-revert
Reverts logical units of work (Tracks, Phases, or Tasks) by analyzing git history and synchronizing the Conductor plans. Use when a user wants to undo specific changes and ensure the project's documentation reflects the rolled-back state.
10conductor-newtrack
Initiates a new unit of work (Track) in a Conductor-managed project. Use when the user wants to start a new feature, fix a bug, or perform maintenance. This skill guides the user through interactive specification building and detailed implementation planning.
9