track-creation

Track Creation Skill

Goal

Create complete Conductor tracks with properly structured spec, plan, and metadata files.

Activation Triggers

• User runs /omg:track with a feature name
• User asks to "start a new track", "create a feature track", or "plan a feature"
• User wants to begin a new Conductor workflow for a feature

Bundled Resources

This skill includes templates that the agent can read and use:

• templates/spec.md - Track specification template
• templates/plan.md - Implementation plan template
• templates/metadata.json - Track metadata template

Process

1. Generate Track ID

Create a unique track ID:

FEATURE_SNAKE=$(echo "{{FEATURE_NAME}}" | tr '[:upper:]' '[:lower:]' | tr ' ' '_' | tr -cd '[:alnum:]_')
DATE=$(date +%Y%m%d)
TRACK_ID="${FEATURE_SNAKE}_${DATE}"
echo $TRACK_ID

2. Create Track Directory

mkdir -p conductor/tracks/${TRACK_ID}

3. Read and Customize Templates

Read each template from this skill's directory, replace placeholders, and write to the track directory.

Placeholders to replace:

• {{FEATURE_NAME}} - User-provided feature name
• {{TRACK_ID}} - Generated track ID
• {{DATE}} - Current date (YYYY-MM-DD)
• {{ISO_TIMESTAMP}} - Current ISO timestamp

4. Gather Requirements

Before writing the spec, ask clarifying questions:

• What problem does this solve?
• Who is the primary user?
• What are the must-have requirements?
• What's explicitly out of scope?

5. Write Files

Create three files in conductor/tracks/${TRACK_ID}/:

1. spec.md - Filled with user's requirements
2. plan.md - Phased implementation tasks
3. metadata.json - Track state tracking

6. Update tracks.md

Add entry to conductor/tracks.md:

## [ ] Track: {{FEATURE_NAME}}
*ID: {{TRACK_ID}}*
*Link: [./tracks/{{TRACK_ID}}/]*
*Status: New*
*Created: {{DATE}}*

7. Verify Creation

ls -la conductor/tracks/${TRACK_ID}/
cat conductor/tracks/${TRACK_ID}/metadata.json