Skip to main content
ClaudeWave
ES, Spanish
Skill286 estrellas del repoactualizado 7mo ago

status

The status skill provides read-only analysis of project progress by parsing Plan.md files and metadata across all conductor tracks. It calculates completion percentages, identifies blocked tasks and current activities, then delivers a summary report with recommended next actions. Use this skill to assess overall project health, spot impediments, and understand which track phase is active.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/MadAppGang/claude-code /tmp/status && cp -r /tmp/status/plugins/conductor/skills/status ~/.claude/skills/status
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

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

Architecture Decision Records (ADR) documentation practice. Use when documenting architectural decisions, recording technical trade-offs, creating decision logs, or establishing architectural patterns. Trigger keywords - "ADR", "architecture decision", "decision record", "trade-offs", "architectural decision", "decision log".

agent-coordination-disciplineSkill

Use when deciding whether to launch an agent, selecting which agent to use, or coordinating multiple agents. Covers delegation criteria, external-model patterns, task isolation, and agent selection strategies.

api-designSkill

Use when designing REST or GraphQL APIs, defining endpoints, implementing pagination/filtering, handling API versioning, or establishing API documentation with OpenAPI/Swagger.

api-integrationSkill

Use when integrating Apidog + OpenAPI specifications with your React app. Covers MCP server setup, type generation, and query layer integration. Use when setting up API clients, generating types from OpenAPI, or integrating with Apidog MCP.

api-spec-analyzerSkill

Analyzes API documentation from OpenAPI specs to provide TypeScript interfaces, request/response formats, and implementation guidance. Use when implementing API integrations, debugging API errors (400, 401, 404), replacing mock APIs, verifying data types, or when user mentions endpoints, API calls, or backend integration.

architect-detectiveSkill

Use when analyzing architecture and system design. Find design patterns, map layers, identify core abstractions via PageRank. Uses claudemem AST structural analysis for efficient architecture investigation.

auditSkill

On-demand security and code quality audit. Use when checking for vulnerabilities, security issues, code smells, or compliance problems. Trigger keywords - "audit", "security check", "vulnerability scan", "code quality", "compliance", "security audit".

auth-patternsSkill

Use when implementing authentication (JWT, sessions, OAuth), authorization (RBAC, ABAC), password hashing, MFA, or security best practices for backend services.