smithery/MadAppGang

status

Show active tracks, progress, current tasks, and blockers

Installation

$ npx skills add smithery/MadAppGang --skill status

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/MadAppGang · top by installs.

npx skills add smithery/MadAppGang

Browse all from smithery/MadAppGang

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,946 B
  • docs SUMMARY.md 71 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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

<readonly> This skill ONLY reads files. It does NOT modify any conductor/ files. For modifications, use other skills. </readonly>

<comprehensivescan> Parse ALL of: - conductor/tracks.md (index) - conductor/tracks//plan.md (all plans) - conductor/tracks//metadata.json (state) </comprehensivescan> </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>

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

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

### Active Tracks: 1

featureauth20260105 - 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 featureauth track. Run: conductor:implement </correctoutput> </example>

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

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

### Active Tracks: 2

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

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

### Next Action Resolve blocker in featureauth (Task 2.4) or complete review of bugfixlogin. </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}

  • {trackid} Task {taskid}: "{blocker_description}"

{/each} {/if}

Active Tracks

{#each activetrack} {trackid} - {title}

  • Progress: [{progress_bar}] {percent}% ({completed}/{total})
  • Phase: {currentphase}/{totalphases} - {phase_name}
  • Current: {currenttaskid} {currenttasktitle}

{/each}

{#if completed_tracks}

Completed Tracks

{#each completed_track}

  • {track_id} - Completed {date}

{/each} {/if}

Next Action

{recommendation} </status_template> </formatting>