status

Show active tracks, progress, current tasks, and blockers

248 stars

Best use case

status is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Show active tracks, progress, current tasks, and blockers

Teams using status should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/status/SKILL.md --create-dirs "https://raw.githubusercontent.com/MadAppGang/claude-code/main/plugins/conductor/skills/status/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/status/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How status Compares

Feature / AgentstatusStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Show active tracks, progress, current tasks, and blockers

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

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_tasks>
      This is a read-only skill that only displays status.
      Tasks are NOT required because there are no implementation phases.
      The skill performs a single atomic operation: read and present status.
    </no_tasks>

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

Related Skills

statusline-customization

248
from MadAppGang/claude-code

Configuration reference and troubleshooting for the statusline plugin — sections, themes, bar widths, and script architecture

test-skill

248
from MadAppGang/claude-code

A test skill for validation testing. Use when testing skill parsing and validation logic.

bad-skill

248
from MadAppGang/claude-code

This skill has invalid YAML in frontmatter

release

248
from MadAppGang/claude-code

Plugin release process for MAG Claude Plugins marketplace. Covers version bumping, marketplace.json updates, git tagging, and common mistakes. Use when releasing new plugin versions or troubleshooting update issues.

openrouter-trending-models

248
from MadAppGang/claude-code

Fetch trending programming models from OpenRouter rankings. Use when selecting models for multi-model review, updating model recommendations, or researching current AI coding trends. Provides model IDs, context windows, pricing, and usage statistics from the most recent week.

Claudish Integration Skill

248
from MadAppGang/claude-code

**Version:** 1.0.0

transcription

248
from MadAppGang/claude-code

Audio/video transcription using OpenAI Whisper. Covers installation, model selection, transcript formats (SRT, VTT, JSON), timing synchronization, and speaker diarization. Use when transcribing media or generating subtitles.

final-cut-pro

248
from MadAppGang/claude-code

Apple Final Cut Pro FCPXML format reference. Covers project structure, timeline creation, clip references, effects, and transitions. Use when generating FCP projects or understanding FCPXML structure.

ffmpeg-core

248
from MadAppGang/claude-code

FFmpeg fundamentals for video/audio manipulation. Covers common operations (trim, concat, convert, extract), codec selection, filter chains, and performance optimization. Use when planning or executing video processing tasks.

technical-audit

248
from MadAppGang/claude-code

Technical SEO audit methodology including crawlability, indexability, and Core Web Vitals analysis. Use when auditing pages or sites for technical SEO issues.

serp-analysis

248
from MadAppGang/claude-code

SERP analysis techniques for intent classification, feature identification, and competitive intelligence. Use when analyzing search results for content strategy.

schema-markup

248
from MadAppGang/claude-code

Schema.org markup implementation patterns for rich results. Use when adding structured data to content for enhanced SERP appearances.