status

Show active tracks, progress, current tasks, and blockers

⭐202stars🔀19forks📁View on GitHub🕐Updated Jan 8, 2026⬇️2downloads

When & Why to Use This Skill

This Claude skill serves as a dedicated Progress Reporter and Status Analyzer, designed to provide a clear, data-driven overview of project health. By parsing plan files and metadata, it automatically calculates completion percentages, identifies critical blockers, and suggests the most impactful next actions to keep workflows moving efficiently.

Use Cases

  • Generating comprehensive status reports for multi-track projects to ensure all stakeholders are aligned on progress.
  • Identifying and highlighting 'Blocked' tasks to prioritize resource allocation and problem-solving.
  • Calculating real-time completion metrics and task distribution (pending, in-progress, complete) for accurate project forecasting.
  • Providing actionable 'Next Step' recommendations to guide developers or agents through complex implementation phases.
namestatus
descriptionShow active tracks, progress, current tasks, and blockers
version1.0.0
tags[conductor, status, progress, overview]
keywords[status, progress, tracks, overview, blockers, current]

plugin: conductor updated: 2026-01-20

Progress Reporter & Status Analyzer - Plan.md parsing and analysis - Progress calculation and visualization - Blocker identification - Multi-track overview Provide clear, actionable status reports that help users understand their project progress, identify next actions, and spot blockers. This is a read-only skill that only displays status. TodoWrite is NOT required because there are no implementation phases. The skill performs a single atomic operation: read and present status.
<read_only>
  This skill ONLY reads files.
  It does NOT modify any conductor/ files.
  For modifications, use other skills.
</read_only>

<comprehensive_scan>
  Parse ALL of:
  - conductor/tracks.md (index)
  - conductor/tracks/*/plan.md (all plans)
  - conductor/tracks/*/metadata.json (state)
</comprehensive_scan>
Always end with clear "Next Action" recommendation. Don't just report status, guide next step.
<principle name="Blocker Visibility" priority="high">
  Prominently display any blocked tasks.
  Blockers need attention.
</principle>
Check conductor/ exists Read conductor/tracks.md for track list For each track, read plan.md and metadata.json
<phase number="2" name="Analysis">
  <step>Count tasks by status: pending, in_progress, complete, blocked</step>
  <step>Calculate completion percentage per track</step>
  <step>Identify current phase and task</step>
  <step>Find any blocked tasks</step>
</phase>

<phase number="3" name="Presentation">
  <step>Display overview summary</step>
  <step>Show per-track details</step>
  <step>Highlight blockers if any</step>
  <step>Recommend next action</step>
</phase>
``` Completion % = (completed_tasks / total_tasks) * 100

Example:

  • Total tasks: 15
  • Completed: 6
  • In Progress: 1
  • Pending: 8
  • Completion: 40%
  </progress_calculation>

  <status_priority>
    Display order by priority:
    1. BLOCKED tasks (need attention)
    2. IN_PROGRESS tasks (current work)
    3. Active tracks summary
    4. Completed tracks (brief)
  </status_priority>
</knowledge>

<examples>
  <example name="Single Active Track">
    <user_request>What's my status?</user_request>
    <correct_output>
      ## Conductor Status

      ### Active Tracks: 1

      **feature_auth_20260105** - User Authentication
      - Progress: [========------] 53% (8/15 tasks)
      - Phase: 2/4 - Core Authentication
      - Current: 2.3 Create login endpoint
      - Blockers: None

      ### Next Action
      Continue task 2.3 (Create login endpoint) in feature_auth track.
      Run: `conductor:implement`
    </correct_output>
  </example>

  <example name="Multiple Tracks with Blocker">
    <user_request>Show me the status</user_request>
    <correct_output>
      ## Conductor Status

      ### BLOCKERS (1)
      - **feature_auth_20260105** Task 2.4: "Waiting for API key from team lead"

      ### Active Tracks: 2

      **feature_auth_20260105** - User Authentication
      - Progress: [=======-------] 47% (7/15 tasks)
      - Phase: 2/4 - Core Authentication
      - Status: BLOCKED at 2.4

      **bugfix_login_20260104** - Login redirect fix
      - Progress: [==============] 100% (5/5 tasks)
      - Status: Ready for review

      ### Next Action
      Resolve blocker in feature_auth (Task 2.4) or complete review of bugfix_login.
    </correct_output>
  </example>
</examples>

<formatting>
  <status_template>
## Conductor Status

### Overview
- Active Tracks: {N}
- Total Progress: {X}% ({completed}/{total} tasks)
- Blockers: {N}

{#if blockers}
### BLOCKERS
{#each blocker}
- **{track_id}** Task {task_id}: "{blocker_description}"
{/each}
{/if}

### Active Tracks
{#each active_track}
**{track_id}** - {title}
- Progress: [{progress_bar}] {percent}% ({completed}/{total})
- Phase: {current_phase}/{total_phases} - {phase_name}
- Current: {current_task_id} {current_task_title}
{/each}

{#if completed_tracks}
### Completed Tracks
{#each completed_track}
- {track_id} - Completed {date}
{/each}
{/if}

### Next Action
{recommendation}
  </status_template>
</formatting>