Conductor New Track FAQs

Question 1

What is a 'Track' in the Conductor framework?

Accepted Answer

A Track is a dedicated unit of work, such as a feature, bug fix, or chore, that includes its own specification, implementation plan, and metadata organized in a specific folder.

Question 2

Does this skill require a specific project setup?

Accepted Answer

Yes, it requires the Conductor environment to be initialized. If your project isn't set up yet, you should run the setup skill first to create core context files like product.md and tech-stack.md.

Question 3

What happens if a track with the same name already exists?

Accepted Answer

The skill performs a collision check against the Tracks Directory and will alert you if a track with that name exists, preventing accidental overwrites.

Question 4

How does the skill determine the implementation tasks?

Accepted Answer

It reads your project's workflow.md file to ensure the implementation plan follows your team's specific methodologies, such as TDD or specific checkpoint protocols.

Question 5

Can I modify the generated plan before it is saved?

Accepted Answer

Absolutely. The skill provides an interactive review phase where you can approve the drafted specification and plan or suggest changes until they meet your requirements.

Conductor New Track

Key Features

Use Cases

Conductor New Track

Key Features

Use Cases