conductor-newTrack

To generate spec and plan files for a new Conductor track, use this skill to answer targeted questions or provide arguments, which automatically creates your spec.md and hierarchical plan.md files.

Yes, you can create Conductor track artifacts without manual repository commits because this skill automatically generates directories, metadata.json, index.md, updates the tracks registry, and commits changes directly.

Automating spec generation in a spec-driven development workflow is best achieved by using interactive prompts that capture feature details to automatically output a structured spec.md document.

Plan generation works by taking your approved specification and project workflow to automatically produce a hierarchical plan.md file outlining the necessary development steps.

No, you do not need to manually update the tracks registry when adding a new feature track, as the skill handles registry updates and commits the repository changes automatically.

Yes, you can define a new Conductor track using command-line arguments instead of interactive questions, as the skill supports both argument-based and interactive track description input methods.