conductor-status

# Conductor Status Display the current status of the Conductor project, including overall progress, active tracks, and next actions. ## Use this skill when - Working on conductor status tasks or workflows - Needing guidance, best practices, or checklists for conductor status ## Do not use this skill when - The task is unrelated to conductor status - You need a different domain or tool outside this scope ## Instructions - Clarify goals, constraints, and required inputs. - Apply relevant best practices and validate outcomes. - Provide actionable steps and verification. - If detailed examples are required, open `resources/implementation-playbook.md`. ## Pre-flight Checks 1. Verify Conductor is initialized: - Check `conductor/product.md` exists - Check `conductor/tracks.md` exists - If missing: Display error and suggest running `/conductor:setup` first 2. Check for any tracks: - Read `conductor/tracks.md` - If no tracks registered: Display setup complete message with suggestion to create first track ## Data Collection ### 1. Project Information Read `conductor/product.md` and extract: - Project name - Project description ### 2. Tracks Overview Read `conductor/tracks.md` and parse: - Total tracks count - Completed tracks (marked `[x]`) - In-progress tracks (marked `[~]`) - Pending tracks (marked `[ ]`) ### 3. Detailed Track Analysis For each track in `conductor/tracks/`: Read `conductor/tracks/{trackId}/plan.md`: - Count total tasks (lines matching `- [x]`, `- [~]`, `- [ ]` with Task prefix) - Count completed tasks (`[x]`) - Count in-progress tasks (`[~]`) - Count pending tasks (`[ ]`) - Identify current phase (first phase with incomplete tasks) - Identify next pending task Read `conductor/tracks/{trackId}/metadata.json`: - Track type (feature, bug, chore, refactor) - Created date - Last updated date - Status Read `conductor/tracks/{trackId}/spec.md`: - Check for any noted blockers or dependencies ### 4. Blocker Detection Scan for potential blockers: - Tasks marked with `BLOCKED:` prefix - Dependencies on incomplete tracks - Failed verification tasks ## Output Format ### Full Project Status (no argument) ``` ================================================================================ PROJECT STATUS: {Project Name} ================================================================================ Last Updated: {current timestamp} -------------------------------------------------------------------------------- OVERALL PROGRESS -------------------------------------------------------------------------------- Tracks: {completed}/{total} completed ({percentage}%) Tasks: {completed}/{total} completed ({percentage}%) Progress: [##########..........] {percentage}% -------------------------------------------------------------------------------- TRACK SUMMARY -------------------------------------------------------------------------------- | Status | Track ID | Type | Tasks | Last Updated | |--------|-------------------|---------|------------|--------------| | [x] | auth_20250110 | feature | 12/12 (100%)| 2025-01-12 | | [~] | dashboard_20250112| feature | 7/15 (47%) | 2025-01-15 | | [ ] | nav-fix_20250114 | bug | 0/4 (0%) | 2025-01-14 | -------------------------------------------------------------------------------- CURRENT FOCUS -------------------------------------------------------------------------------- Active Track: dashboard_20250112 - Dashboard Feature Current Phase: Phase 2: Core Components Current Task: [~] Task 2.3: Implement chart rendering Progress in Phase: - [x] Task 2.1: Create dashboard layout - [x] Task 2.2: Add data fetching hooks - [~] Task 2.3: Implement chart rendering - [ ] Task 2.4: Add filter controls -------------------------------------------------------------------------------- NEXT ACTIONS -------------------------------------------------------------------------------- 1. Complete: Task 2.3 - Implement chart rendering (dashboard_20250112) 2. Then: Task 2.4 - Add filter controls (dashboard_20250112) 3. After Phase 2: Phase verification checkpoint -------------------------------------------------------------------------------- BLOCKERS -------------------------------------------------------------------------------- {If blockers found:} ! BLOCKED: Task 3.1 in dashboard_20250112 depends on api_20250111 (incomplete) {If no blockers:} No blockers identified. ================================================================================ Commands: /conductor:implement {trackId} | /conductor:new-track | /conductor:revert ================================================================================ ``` ### Single Track Status (with track-id argument) ``` ================================================================================ TRACK STATUS: {Track Title} ================================================================================ Track ID: {trackId} Type: {feature|bug|chore|refactor} Status: {Pending|In Progress|Complete} Created: {date} Updated: {date}