Conductor Track Management FAQs

Question 1

How does the skill handle track dependencies?

Accepted Answer

The skill allows you to identify and document hard, soft, and external dependencies within the spec.md file. It provides specific status markers ([!]) to indicate when tasks or entire tracks are blocked by dependencies.

Question 2

What is a 'track' in the Conductor system?

Accepted Answer

A track is a logical work unit that encapsulates a complete piece of work, such as a feature or bug fix. It includes a unique ID, a specification (spec.md), a phased implementation plan (plan.md), and metadata for tracking progress.

Question 3

Does this skill integrate with Git?

Accepted Answer

Yes. The skill is designed for Git-aware operations, encouraging the recording of commit SHAs for completed tasks and checkpoints, which enables precise progress tracking and the ability to revert work by track.

Question 4

How do I create a new work unit using this skill?

Accepted Answer

You can initiate the process using the /conductor:new-track command. The skill will guide you through an interactive Q&A to define requirements, identify acceptance criteria, and generate the necessary documentation files.

Question 5

What are the different types of tracks available?

Accepted Answer

Conductor supports four primary track types: 'feature' for new functionality, 'bug' for defect fixes, 'chore' for maintenance tasks, and 'refactor' for code improvements without behavior changes.

Conductor Track Management

주요 기능

사용 사례

Conductor Track Management

주요 기능

사용 사례