How does the skill ensure tasks are manageable?

It follows strict principles that limit phases to 2-6 and tasks to 2-5 per phase, ensuring each item is estimable (roughly 1-4 hours) and independent.

Does this skill require a specific project structure?

Yes, it requires a conductor/ directory containing product.md, tech-stack.md, and workflow.md to provide the necessary context for generating accurate plans.

Can I use this for bug fixes as well as new features?

Absolutely. The skill supports various track types including Feature, Bugfix, Refactor, and General Task, adjusting the planning structure and phase count based on the work type.

What is a 'track' in the Conductor plugin?

A track is a structured unit of work, such as a feature or bug fix, consisting of a technical specification (spec.md), a phased implementation plan (plan.md), and metadata for tracking progress.

Conductor New Track

Name: Conductor New Track
Author: MadAppGang

byMadAppGang

•

211

Collaboration Tools

Generates comprehensive development specifications and hierarchical implementation plans through an interactive Q&A process.

About

The new-track skill transforms project requirements into structured, actionable development paths within the Conductor framework. By leveraging existing project context—such as tech stacks and product goals—it guides developers through a systematic workflow to create detailed specifications and multi-phase plans. This skill ensures consistency in project tracking, task estimation, and execution strategy, making it an essential tool for managing features, bug fixes, and refactoring efforts with precision.

Key Features

Context-aware planning using project-specific technical and product documentation
Standardized track identification and automated file management
Interactive requirements elicitation via guided Q&A
Automatic generation of hierarchical phases, tasks, and subtasks
Integrated progress tracking with TodoWrite support
211 GitHub stars

Use Cases

Scoping out a complex new feature with multi-stage milestones and acceptance criteria
Planning a code refactor with clear before-and-after comparison phases and technical constraints
Breaking down a critical bug fix into reproduction, resolution, and verification steps

About

Key Features

Context-aware planning using project-specific technical and product documentation
Standardized track identification and automated file management
Interactive requirements elicitation via guided Q&A
Automatic generation of hierarchical phases, tasks, and subtasks
Integrated progress tracking with TodoWrite support
211 GitHub stars

Use Cases

Scoping out a complex new feature with multi-stage milestones and acceptance criteria
Planning a code refactor with clear before-and-after comparison phases and technical constraints
Breaking down a critical bug fix into reproduction, resolution, and verification steps