---
phase: 04-core-track-production
plan: 01
type: execute
wave: 1
depends_on: []
files_modified:
  - .claude/skills/create-track/SKILL.md
  - .claude/skills/create-track/steps/01-collect-inputs.md
autonomous: true

must_haves:
  truths:
    - "User can invoke /create-track [artist] [concept] and Claude loads the skill"
    - "Step 01 validates the artist exists, loads the bible, collects concept/mood/language, identifies the song template, and presents a creative direction summary"
    - "SKILL.md defines a 3-step sequential workflow with persona, arguments, references, and rules"
  artifacts:
    - path: ".claude/skills/create-track/SKILL.md"
      provides: "Track creation skill orchestrator"
      contains: "name: create-track"
    - path: ".claude/skills/create-track/steps/01-collect-inputs.md"
      provides: "Input collection and artist context loading step"
      contains: "bible.md"
  key_links:
    - from: ".claude/skills/create-track/SKILL.md"
      to: "steps/01-collect-inputs.md"
      via: "Read steps/01-collect-inputs.md instruction in Step 1 section"
      pattern: "01-collect-inputs"
    - from: ".claude/skills/create-track/steps/01-collect-inputs.md"
      to: "artists/[name]/bible.md"
      via: "Artist existence check and bible loading"
      pattern: "bible\\.md"
    - from: ".claude/skills/create-track/steps/01-collect-inputs.md"
      to: "reference/templates/songs/"
      via: "Genre-to-template mapping for song structure selection"
      pattern: "templates/songs"
---

<objective>
Create the track creation skill entry point (SKILL.md) and Step 01 (collect inputs) that together enable users to invoke /create-track and begin the track production workflow.

Purpose: Establishes the skill architecture and the first interaction -- loading the artist identity, collecting the track concept/mood/language, and preparing the creative direction before lyrics generation.

Output: 2 markdown files forming the skill entry point and input collection step, mirroring the create-artist skill pattern but adapted for a 3-step directed creative workflow.
</objective>

<execution_context>
@C:/Users/zekho/.claude/get-shit-done/workflows/execute-plan.md
@C:/Users/zekho/.claude/get-shit-done/templates/summary.md
</execution_context>

<context>
@.planning/PROJECT.md
@.planning/ROADMAP.md
@.planning/STATE.md
@.planning/phases/04-core-track-production/04-RESEARCH.md

# Existing skill pattern to replicate
@.claude/skills/create-artist/SKILL.md

# Reference files the skill will point to
@reference/suno/format.md
@reference/templates/songs/README.md
@reference/templates/discography-template.md
@CLAUDE.md
</context>

<tasks>

<task type="auto">
  <name>Task 1: Create SKILL.md skill orchestrator for create-track</name>
  <files>.claude/skills/create-track/SKILL.md</files>
  <action>
Create `.claude/skills/create-track/SKILL.md` following the exact same Claude Code skill frontmatter pattern as `.claude/skills/create-artist/SKILL.md`.

**Frontmatter (3 fields only -- per decision [02-02]):**
- `name: create-track`
- `description: Create a complete track production brief for an existing artist. Generates singable lyrics with Suno section tags, a style prompt, and a Suno-ready production brief. Use when the user wants to create a new track, write a song, or produce music for an artist.`
- `argument-hint: "[artist-name] [concept/mood]"`

**Body structure (mirror create-artist SKILL.md):**

1. **# Create Track** -- title

2. **## Persona** -- Collaborateur creatif enthousiaste specialise dans l'ecriture de lyrics. Produit des lyrics singables, emotionnellement justes, et structurellement solides pour Suno. Parle en francais par defaut. Engage avec la vision creative de l'utilisateur.

3. **## Arguments** -- `$ARGUMENTS` contient le nom de l'artiste et optionnellement un concept/mood. Si l'artiste n'est pas fourni, demander quel artiste. Si le concept n'est pas fourni, le collecter dans Step 1.

4. **## Processus** -- 3 etapes sequentielles. Explain: plus compact que le wizard artiste -- le track creation est une production dirigee, pas une exploration.
   - Include rules: travailler chaque etape dans l'ordre, lire le fichier de l'etape, respecter les contraintes de la bible, ne jamais ecrire de fichier avant Step 3.

5. **## Etapes** -- 3 steps:
   - **Etape 1: Inputs et Direction** -- Lire `steps/01-collect-inputs.md`
   - **Etape 2: Structure et Ecriture** -- Lire `steps/02-structure-and-write.md`
   - **Etape 3: Verification et Sauvegarde** -- Lire `steps/03-verify-and-save.md`

6. **## Output** -- Describe what gets written: track file at `artists/[name]/tracks/[##]-[titre-kebab].md` and discography update at `artists/[name]/discography.md`.

7. **## References** -- List all reference files:
   - Bible artiste: `artists/[name]/bible.md`
   - Song templates: `reference/templates/songs/`
   - Suno reference: `reference/suno/format.md`
   - Production format: voir CLAUDE.md section "Format de Production"
   - Glossaire: `reference/glossary.md`
   - Conventions artistes: `artists/README.md`

8. **## Regles** -- 7 behavioral rules (numbered):
   1. La bible est la loi -- zero deviation du genre, style vocal, themes, emotions
   2. Une langue par track -- pas de melange
   3. Chaque Verse avance la narration ou explore un nouvel angle -- pas de repetition
   4. Le Chorus est memorable, concis, capture le coeur emotionnel
   5. Auto-save -- ecrire le fichier sans demander confirmation (mais presenter les lyrics au user d'abord dans Step 2)
   6. Toujours fournir un raisonnement creatif
   7. Verifier les contraintes Suno avant d'ecrire (style prompt <= 1000 chars, lyrics <= 3000 chars recommande, <= 5000 max)

Total: ~80-90 lines. Keep it lean -- the skill orchestrates, the step files contain the detailed instructions.
  </action>
  <verify>
- File exists at `.claude/skills/create-track/SKILL.md`
- Frontmatter has exactly 3 fields: name, description, argument-hint
- References all 3 step files by correct paths
- Lists all reference files (bible, templates, format.md, glossary, README)
- Contains 7 behavioral rules
- Does NOT contain domain knowledge that belongs in step files or reference files
  </verify>
  <done>SKILL.md is a complete skill orchestrator that Claude can load when the user invokes /create-track, defining the 3-step workflow, persona, references, and behavioral rules</done>
</task>

<task type="auto">
  <name>Task 2: Create Step 01 -- Collect Inputs and Load Artist Context</name>
  <files>.claude/skills/create-track/steps/01-collect-inputs.md</files>
  <action>
Create `.claude/skills/create-track/steps/01-collect-inputs.md` following the research's Pattern 2 specification.

**# Step 1 : Inputs et Direction Creative**

**## Champs a Collecter** -- two subsections:
- **Obligatoires:** Artiste (nom, verifier bible exists), Concept/Mood (idee, theme, emotion, ambiance), Langue (Francais ou English)
- **Optionnels:** Titre (si l'utilisateur en a un), Structure (variation specifique du template)

**## Process** -- 6 numbered operations:
1. Verifier l'existence de `artists/[name-in-kebab-case]/bible.md`. Si absent: "Cet artiste n'existe pas encore. Utilisez /create-artist [nom] d'abord." -- stop workflow.
2. Lire la bible complete. Extract: genre, sous-genres, tempo range, vocal style, Tags Suno, emotions (primaires, secondaires, interdites), themes, lore, regles de coherence.
3. Lire `artists/[name]/discography.md` pour determiner le prochain numero de track (count existing table rows + 1).
4. Identifier le template de structure adapte au genre dans `reference/templates/songs/`. Mapping logic: check genre and subgenres against template `aliases` frontmatter. If no match, use pop.md as safe default and note the adaptation.
5. Collecter concept/mood et langue si non fournis dans $ARGUMENTS. Keep it to 1-2 exchanges max -- this is not an exploration wizard.
6. Presenter un resume de la direction creative:
   - Artiste: [nom] ([genre])
   - Concept: [concept fourni par l'utilisateur]
   - Langue: [langue choisie]
   - Structure: [template selectionne + notation (e.g., "Pop ABABCB")]
   - Emotions a explorer: [emotions de la palette qui matchent le concept]
   - Track #: [prochain numero]

**## Genre-Template Mapping** -- Quick reference table:
| Template | Genres couverts (aliases) |
|----------|--------------------------|
| pop.md | Pop, Synth-Pop, Electro-Pop, Indie Pop, Art Pop, Dark Pop, Bedroom Pop |
| rap.md | Rap, Hip-Hop, Trap, Drill, Boom Bap, Cloud Rap, Conscious Rap |
| ballad.md | Ballad, Power Ballad, Acoustic Ballad, Folk Ballad |
| rock.md | Rock, Indie Rock, Alt Rock, Post-Punk, Grunge, Punk Rock |
| electronic.md | Electronic, EDM, House, Techno, Synthwave, Ambient, Drum and Bass |
| (default) | pop.md pour tout genre non couvert |

Note: Read the actual aliases from each template's frontmatter at runtime -- this table is a quick reference, not the source of truth.

**## Validation** -- Checklist:
- [ ] L'artiste existe (bible.md trouvee)
- [ ] Le concept/mood est fourni (non vide)
- [ ] La langue est choisie (Francais ou English uniquement)
- [ ] Un template de structure est identifie pour le genre
- [ ] Les regles de coherence de la bible sont lues (ne pas generer de tracks dans les emotions interdites)

Total: ~60-70 lines.
  </action>
  <verify>
- File exists at `.claude/skills/create-track/steps/01-collect-inputs.md`
- Contains artist existence verification with error message
- References bible.md, discography.md, and reference/templates/songs/
- Includes genre-to-template mapping logic
- Lists both obligatory and optional fields
- Has a validation checklist at the end
- Does NOT generate lyrics (that is Step 02)
  </verify>
  <done>Step 01 file provides complete instructions for collecting inputs, loading the artist bible, selecting the song template, and presenting a creative direction summary before lyrics generation begins</done>
</task>

</tasks>

<verification>
1. Both files exist in `.claude/skills/create-track/`
2. SKILL.md frontmatter uses only the 3 valid fields (name, description, argument-hint)
3. SKILL.md references all 3 step files with correct relative paths
4. Step 01 validates artist existence before proceeding
5. Step 01 uses discography.md (not filename counting) for track numbering
6. Neither file duplicates content from reference files (format.md, glossary.md, etc.)
</verification>

<success_criteria>
- A user can invoke /create-track and Claude loads the SKILL.md orchestrator
- Claude reads Step 01 and knows exactly how to validate the artist, load context, and present a creative direction summary
- The skill defines a clear 3-step workflow boundary: Step 1 = inputs, Step 2 = write, Step 3 = save
- All rules from CLAUDE.md are reflected in the skill's behavioral rules
</success_criteria>

<output>
After completion, create `.planning/phases/04-core-track-production/04-01-SUMMARY.md`
</output>
