conductor-status
Helps your agent show project status. It informs which tasks are active and what the next actions are.
What it does
This tool shows the progress of a project called Conductor. It tells you which parts of the project are active, what needs to be done next, and if any issues are blocking progress.
When to use it
- ✓When you want to know the overall status of a project.
- ✓When you need to know which tasks are in progress or pending.
- ✓When you want to identify if something is blocking the project's advancement.
Example of what to ask your AI
“What is the current status of the Conductor project?”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
The tool checks specific project files to gather information about task progress and active components. It organizes this information to present a clear summary.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add sickn33/agentic-awesome-skills --skill conductor-statusOr download just the file:
curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/conductor-status/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
Conductor Status
Display the current status of the Conductor project, including overall progress, active tracks, and next actions.
Use this skill when
- Working on conductor status tasks or workflows
- Needing guidance, best practices, or checklists for conductor status
Do not use this skill when
- The task is unrelated to conductor status
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
Pre-flight Checks
Verify Conductor is initialized:
- Check
conductor/product.mdexists - Check
conductor/tracks.mdexists - If missing: Display error and suggest running
/conductor:setupfirst
- Check
Check for any tracks:
- Read
conductor/tracks.md - If no tracks registered: Display setup complete message with suggestion to create first track
- Read
Data Collection
1. Project Information
Read conductor/product.md and extract:
- Project name
- Project description
2. Tracks Overview
Read conductor/tracks.md and parse:
- Total tracks count
- Completed tracks (marked
[x]) - In-progress tracks (marked
[~]) - Pending tracks (marked
[ ])
3. Detailed Track Analysis
For each track in conductor/tracks/:
Read conductor/tracks/{trackId}/plan.md:
- Count total tasks (lines matching
- [x],- [~],- [ ]with Task prefix) - Count completed tasks (
[x]) - Count in-progress tasks (
[~]) - Count pending tasks (
[ ]) - Identify current phase (first phase with incomplete tasks)
- Identify next pending task
Read conductor/tracks/{trackId}/metadata.json:
- Track type (feature, bug, chore, refactor)
- Created date
- Last updated date
- Status
Read conductor/tracks/{trackId}/spec.md:
- Check for any noted blockers or dependencies
4. Blocker Detection
Scan for potential blockers:
- Tasks marked with
BLOCKED:prefix - Dependencies on incomplete tracks
- Failed verification tasks
Output Format
Full Project Status (no argument)
================================================================================
PROJECT STATUS: {Project Name}
================================================================================
Last Updated: {current timestamp}
--------------------------------------------------------------------------------
OVERALL PROGRESS
--------------------------------------------------------------------------------
Tracks: {completed}/{total} completed ({percentage}%)
Tasks: {completed}/{total} completed ({percentage}%)
Progress: [##########..........] {percentage}%
--------------------------------------------------------------------------------
TRACK SUMMARY
--------------------------------------------------------------------------------
| Status | Track ID | Type | Tasks | Last Updated |
|--------|-------------------|---------|------------|--------------|
| [x] | auth_20250110 | feature | 12/12 (100%)| 2025-01-12 |
| [~] | dashboard_20250112| feature | 7/15 (47%) | 2025-01-15 |
| [ ] | nav-fix_20250114 | bug | 0/4 (0%) | 2025-01-14 |
--------------------------------------------------------------------------------
CURRENT FOCUS
--------------------------------------------------------------------------------
Active Track: dashboard_20250112 - Dashboard Feature
Current Phase: Phase 2: Core Components
Current Task: [~] Task 2.3: Implement chart rendering
Progress in Phase:
- [x] Task 2.1: Create dashboard layout
- [x] Task 2.2: Add data fetching hooks
- [~] Task 2.3: Implement chart rendering
- [ ] Task 2.4: Add filter controls
--------------------------------------------------------------------------------
NEXT ACTIONS
--------------------------------------------------------------------------------
1. Complete: Task 2.3 - Implement chart rendering (dashboard_20250112)
2. Then: Task 2.4 - Add filter controls (dashboard_20250112)
3. After Phase 2: Phase verification checkpoint
--------------------------------------------------------------------------------
BLOCKERS
--------------------------------------------------------------------------------
{If blockers found:}
…
FAQ
What are 'tracks'?
'Tracks' are like specific steps or parts of the project that are being worked on.
How does the tool know what's blocking the project?
It looks for tasks marked as 'blocked' or for dependencies on other project parts that haven't been completed yet.
Can I use this for any project?
No, this tool is specific to projects using the 'Conductor' methodology and that have the status files correctly configured.
Details
Original description by the author
Display project status, active tracks, and next actions
Popularity
- GitHub stars
- 48k
- Ranking position
- #2621
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
00-andruia-consultant
Helps your agent start or improve AI projects. It analyzes code, suggests tools, and creates action plans in Spanish.
sickn33/agentic-awesome-skills
007
Lets your agent perform security audits and threat modeling. It's useful for protecting projects against attacks and vulnerabilities.
sickn33/agentic-awesome-skills
10-andruia-skill-smith
Helps your agent create or improve AI tools. It defines how tools work, writes documentation, and validates the structure.
sickn33/agentic-awesome-skills
20-andruia-niche-intelligence
Lets your agent create a summary about a specific industry. It's useful for understanding the context, rules, usage patterns, and risks of a project, using reliable sources.
sickn33/agentic-awesome-skills
Similar skills
benchmark-optimization-loop
Has your agent improve something's speed in a measured way. It tests multiple versions and chooses the fastest one that still works correctly.
affaan-m/ECC
change-impact
Helps your agent analyze the impact of code changes before making them. It compares the planned vs. actual results afterward, covering paths, data, tests, and documentation. Useful for risky or system-wide changes.
affaan-m/ECC
click-path-audit
Lets your agent trace all user buttons and interactions to find bugs. It finds issues where functions seem to work alone but fail together. Useful when bugs persist even after debugging.
affaan-m/ECC