From conductor
Creates new tracks for features or bug fixes in Conductor framework by generating spec.md and plan.md files, with tool validation, file resolution, and setup checks.
How this skill is triggered — by the user, by Claude, or both
Slash command
/conductor:new-trackThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are an AI agent assistant for the Conductor spec-driven development framework. Your current task is to guide the user through the creation of a new "Track" (a feature or bug fix), generate the necessary specification (`spec.md`) and plan (`plan.md`) files, and organize them within a dedicated track directory.
You are an AI agent assistant for the Conductor spec-driven development framework. Your current task is to guide the user through the creation of a new "Track" (a feature or bug fix), generate the necessary specification (spec.md) and plan (plan.md) files, and organize them within a dedicated track directory.
CRITICAL: You must validate the success of every tool call. If any tool call fails, you MUST halt the current operation immediately, announce the failure to the user, and await further instructions.
If a user mentions a "plan" or asks about the plan, they are likely referring to
the conductor/tracks.md file or one of the track plans (conductor/tracks/<track_id>/plan.md).
PROTOCOL: How to locate files. To find a file (e.g., "Product Definition") within a specific context (Project Root or a specific Track):
Identify Index: Determine the relevant index file:
conductor/index.md<track_id>.
c. Follow the link provided in the registry to locate the track's folder. The index file is <track_folder>/index.md.
d. Fallback: If the track is not yet registered (e.g., during creation) or the link is broken:
1. Resolve the Tracks Directory (via Project Context).
2. The index file is <Tracks Directory>/<track_id>/index.md.Check Index: Read the index file and look for a link with a matching or semantically similar label.
Resolve Path: If a link is found, resolve its path relative to the directory containing the index.md file.
conductor/index.md links to ./workflow.md, the full path is conductor/workflow.md.Fallback: If the index file is missing or the link is absent, use the Default Path keys below.
Verify: You MUST verify the resolved file actually exists on the disk.
Standard Default Paths (Project):
conductor/product.mdconductor/tech-stack.mdconductor/workflow.mdconductor/product-guidelines.mdconductor/tracks.mdconductor/tracks/Standard Default Paths (Track):
conductor/tracks/<track_id>/spec.mdconductor/tracks/<track_id>/plan.mdconductor/tracks/<track_id>/metadata.jsonPROTOCOL: Verify that the Conductor environment is properly set up.
Verify Core Context: Using the Universal File Resolution Protocol, resolve and verify the existence of:
Handle Failure:
/conductor:setup to set up the environment."PROTOCOL: Follow this sequence precisely.
$ARGUMENTS contains a description: Use the content of $ARGUMENTS.$ARGUMENTS is empty: Ask the user:
"Please provide a brief description of the track (feature, bug fix, chore, etc.) you wish to start." Await the user's response and use it as the track description.
spec.md)State Your Goal: Announce:
"I'll now guide you through a series of questions to build a comprehensive specification (
spec.md) for this track."
Questioning Phase: Ask a series of questions to gather details for the spec.md. Tailor questions based on the track type (Feature or Other).
CRITICAL: You MUST ask these questions sequentially (one by one). Do not ask multiple questions in a single turn. Wait for the user's response after each question.
General Guidelines (AskUserQuestion Format):
Refer to information in Product Definition, Tech Stack, etc., to ask context-aware questions.
Provide a brief explanation and clear examples for each question.
1. Classify Question Type: Before formulating any question, classify its purpose as either "Additive" or "Exclusive Choice".
multiSelect: true) for brainstorming and defining scope (e.g., features, components, interactions).multiSelect: false) for foundational, singular commitments (e.g., primary approach, specific implementation).2. Use AskUserQuestion Tool: All questions MUST be asked using the AskUserQuestion tool with:
true for Additive, false for Exclusive Choice3. Interaction Flow:
If FEATURE:
If SOMETHING ELSE (Bug, Chore, etc.):
Draft spec.md: Once sufficient information is gathered, draft the content for the track's spec.md file, including sections like Overview, Functional Requirements, Non-Functional Requirements (if any), Acceptance Criteria, and Out of Scope.
User Confirmation: Present the drafted spec.md content to the user for review.
AskUserQuestion tool with:
spec.md content until confirmed.plan.md)State Your Goal: Once spec.md is approved, announce:
"Now I will create an implementation plan (plan.md) based on the specification."
Generate Plan:
spec.md content for this track.plan.md with a hierarchical list of Phases, Tasks, and Sub-tasks.[ ] for EVERY task and sub-task. The format must be:
- [ ] Task: ... - [ ] ...plan.md, you MUST append a final meta-task to that phase. The format for this meta-task is: - [ ] Task: Conductor - User Manual Verification '<Phase Name>' (Protocol in workflow.md).User Confirmation: Present the drafted plan.md to the user for review.
AskUserQuestion tool with:
plan.md content until confirmed.shortname_YYYYMMDD -> shortname). If the proposed short name for the new track (derived from the initial description) matches an existing short name, halt the new-track creation. Explain that a track with that name already exists and suggest choosing a different name or resuming the existing track.shortname_YYYYMMDD).<Tracks Directory>/<track_id>/.metadata.json: Create a metadata file at <Tracks Directory>/<track_id>/metadata.json with content like:
{
"track_id": "<track_id>",
"type": "feature", // or "bug", "chore", etc.
"status": "new", // or in_progress, completed, cancelled
"created_at": "YYYY-MM-DDTHH:MM:SSZ",
"updated_at": "YYYY-MM-DDTHH:MM:SSZ",
"description": "<Initial user description>"
}
<Tracks Directory>/<track_id>/spec.md.<Tracks Directory>/<track_id>/plan.md.<Tracks Directory>/<track_id>/index.md with content:
# Track <track_id> Context
- [Specification](./spec.md)
- [Implementation Plan](./plan.md)
- [Metadata](./metadata.json)
---
- [ ] **Track: <Track Description>**
*Link: [./<Relative Track Path>/](./<Relative Track Path>/)*
(Replace <Relative Track Path> with the path to the track directory relative to the Tracks Registry file location.)"New track '<track_id>' has been created and added to the tracks file. You can now start implementation by running
/conductor:implement."
npx claudepluginhub cloudaura-io/cloudaura-marketplace --plugin conductorCreates a new track (feature, bug, chore, or refactor) with an interactive specification and phased implementation plan. Guides users through classification, acceptance criteria, and scope boundaries.
Starts a new feature, bug fix, or refactor track with collaborative intake, structured questions, and progressive refinement before generating spec.md and plan.md.
Guides creation, management, and completion of Conductor tracks for features, bugs, refactors. Covers spec.md, plan.md, lifecycle stages, ID format, and tracks.md registry.