home / skills / madappgang / claude-code / status

This skill reads project status from conductor tracks and plans to deliver actionable progress, blockers, and next actions.

npx playbooks add skill madappgang/claude-code --skill status

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
4.8 KB
---
name: status
description: Show active tracks, progress, current tasks, and blockers
version: 1.0.0
tags: [conductor, status, progress, overview]
keywords: [status, progress, tracks, overview, blockers, current]
---
plugin: conductor
updated: 2026-01-20

<role>
  <identity>Progress Reporter & Status Analyzer</identity>
  <expertise>
    - Plan.md parsing and analysis
    - Progress calculation and visualization
    - Blocker identification
    - Multi-track overview
  </expertise>
  <mission>
    Provide clear, actionable status reports that help users understand
    their project progress, identify next actions, and spot blockers.
  </mission>
</role>

<instructions>
  <critical_constraints>
    <no_todowrite>
      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.
    </no_todowrite>

    <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>
  </critical_constraints>

  <core_principles>
    <principle name="Actionable Output" priority="critical">
      Always end with clear "Next Action" recommendation.
      Don't just report status, guide next step.
    </principle>

    <principle name="Blocker Visibility" priority="high">
      Prominently display any blocked tasks.
      Blockers need attention.
    </principle>
  </core_principles>

  <workflow>
    <phase number="1" name="Data Collection">
      <step>Check conductor/ exists</step>
      <step>Read conductor/tracks.md for track list</step>
      <step>For each track, read plan.md and metadata.json</step>
    </phase>

    <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>
  </workflow>
</instructions>

<knowledge>
  <progress_calculation>
```
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>

Overview

This skill displays current project status by reading conductor tracks, plans, and metadata and presenting a concise progress report. It highlights active tracks, computes completion percentages, surfaces blocked tasks, and ends with a clear next action recommendation. The output is read-only and intended to guide immediate decisions.

How this skill works

The skill scans conductor/tracks.md to discover tracks, then parses each track's plan.md and metadata.json to count task states. It classifies tasks as pending, in_progress, complete, or blocked, calculates per-track and overall completion percentages, and identifies the current phase and active task. Results are presented with prioritized visibility for blockers and a single actionable next step.

When to use it

  • Quickly assess overall project health across multiple work tracks.
  • Identify and surface blockers that require immediate attention.
  • Prepare a short status summary for standups or coordination meetings.
  • Decide the next concrete action when multiple tracks compete for resources.
  • Verify progress numbers before a review or demo.

Best practices

  • Run this skill after any major plan changes to get an accurate snapshot.
  • Keep plan.md and metadata.json up to date so percentages and current tasks reflect reality.
  • Prioritize resolving blocked tasks listed at the top of the report.
  • Use the Next Action recommendation to assign a clear owner and follow-up.
  • Treat this skill as read-only; use separate workflows to modify plans or tasks.

Example use cases

  • Daily standup: generate a one-page status with blockers and the recommended next step.
  • Release readiness check: confirm completion percentages across release-related tracks.
  • Escalation triage: quickly find which track and task is blocking progress.
  • Cross-team coordination: share concise progress bars and current tasks with stakeholders.

FAQ

Does this skill modify any files?

No. It is strictly read-only and only reads conductor/tracks.md, plan.md files, and metadata.json.

How does it show priorities among tracks?

Blockers are shown first, then in-progress tasks, active tracks, and finally completed tracks for brevity.