track-manager | conductor | ClaudePluginHub

Skill

Community

track-manager

16

Description

Manage Conductor tracks, phases, and tasks. Use when working with track status, updating task markers, or navigating between tracks.

AI Summary

Manages Conductor track lifecycle by updating task markers, transitioning phases, and checking progress. Triggers when you mark tasks complete, start new tasks, or ask about track status.

Install

1

Add the repository(one-time)

$

/plugin marketplace add pilotparpikhodjaev/conductor_cc

2

Install the plugin

$

/plugin install conductor@conductor-cc

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Skill Content

Track Manager Skill

Manage the lifecycle of Conductor tracks including status updates, task completion, and phase transitions.

Trigger Conditions

Use this skill when:

Checking track status or progress
Marking tasks as complete
Transitioning between phases
User mentions: "track status", "mark complete", "next task", "update plan"

Track Structure

conductor/
├── tracks.md           # Master track list
└── tracks/
    └── <track_id>/
        ├── spec.md         # Requirements
        ├── plan.md         # Phased tasks
        └── metadata.json   # Status, timestamps

Task Status Markers

Marker	Status	Description
`[ ]`	Pending	Not started
`[~]`	In Progress	Currently working
`[x]`	Completed	Done (add commit SHA)

Workflow Operations

Start a Task

# Before

- [ ] Implement user authentication

# After (mark in progress)

- [~] Implement user authentication

Complete a Task

# After completion (add commit SHA)

- [x] Implement user authentication <!-- abc1234 -->

Update tracks.md

When completing a phase, update conductor/tracks.md:

## Active Tracks

| Track ID | Type    | Status      | Progress  |
| -------- | ------- | ----------- | --------- |
| auth-001 | feature | in_progress | Phase 2/3 |

Phase Transition Rules

All tasks in phase must be [x] before moving to next phase
Update metadata.json with completion timestamp
Create commit for phase completion
Update tracks.md progress column

Response Format

After track operations:

## Track Update

**Track**: [track_id]
**Operation**: [started/completed/updated]
**Phase**: [phase number] - [phase name]
**Progress**: [completed]/[total] tasks
**Next**: [next task description]

Links

GitHub Stats

0 forks

Updated 13 days ago

Similar Skills

Command Development

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

53.4k

Agent Development

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

53.4k

Hook Development

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

53.4k