status
Show active tracks, progress, current tasks, and blockers
What this skill does
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 in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.