---
phase: 02-artist-creation-wizard
plan: 02
type: execute
wave: 2
depends_on: ["02-01"]
files_modified:
  - .claude/skills/create-artist/SKILL.md
  - .claude/skills/create-artist/steps/01-identity.md
  - .claude/skills/create-artist/steps/02-vocal.md
  - .claude/skills/create-artist/steps/03-emotions-themes.md
  - .claude/skills/create-artist/steps/04-personality-lore.md
  - .claude/skills/create-artist/steps/05-visual.md
  - .claude/skills/create-artist/steps/06-review-validate.md
autonomous: true

must_haves:
  truths:
    - "User can invoke the create-artist skill and be guided through a 6-step wizard"
    - "Each wizard step collects specific identity data with suggestions and validation rules"
    - "The wizard validates no critical fields are empty before writing the bible"
    - "The wizard presents the complete bible for review before writing files"
    - "Upon completion the wizard writes bible.md, discography.md, and creates tracks/ directory"
  artifacts:
    - path: ".claude/skills/create-artist/SKILL.md"
      provides: "Wizard orchestrator with skill frontmatter and step-by-step flow"
      contains: "name: create-artist"
    - path: ".claude/skills/create-artist/steps/01-identity.md"
      provides: "Step 1 instructions: name, genre, subgenres, languages, tempo"
      contains: "Genre principal"
    - path: ".claude/skills/create-artist/steps/02-vocal.md"
      provides: "Step 2 instructions: voice type, style, techniques, register, Suno tags"
      contains: "Style vocal"
    - path: ".claude/skills/create-artist/steps/03-emotions-themes.md"
      provides: "Step 3 instructions: emotion palette and thematic universe"
      contains: "Emotions Primaires"
    - path: ".claude/skills/create-artist/steps/04-personality-lore.md"
      provides: "Step 4 instructions: personality traits, bio, tagline, backstory"
      contains: "Personnalite"
    - path: ".claude/skills/create-artist/steps/05-visual.md"
      provides: "Step 5 instructions: color palette, aesthetic style, visual keywords"
      contains: "Direction Visuelle"
    - path: ".claude/skills/create-artist/steps/06-review-validate.md"
      provides: "Step 6 instructions: review, validate completeness, write files"
      contains: "Validation"
  key_links:
    - from: ".claude/skills/create-artist/SKILL.md"
      to: ".claude/skills/create-artist/steps/"
      via: "SKILL.md references each step file sequentially"
      pattern: "steps/0[1-6]"
    - from: ".claude/skills/create-artist/SKILL.md"
      to: "reference/templates/bible-template.md"
      via: "Output section references bible template as structural schema"
      pattern: "bible-template"
    - from: ".claude/skills/create-artist/steps/01-identity.md"
      to: "reference/suno/format.md"
      via: "Step 1 references Suno format for genre/subgenre options"
      pattern: "reference/suno/format.md"
    - from: ".claude/skills/create-artist/steps/06-review-validate.md"
      to: "reference/templates/bible-template.md"
      via: "Validation step uses template as structural contract"
      pattern: "bible-template"
---

<objective>
Create the complete create-artist skill: SKILL.md orchestrator and 6 step files that guide the user through interactive artist creation.

Purpose: This is the first interactive workflow in the project. The skill turns artist creation from a blank-page exercise into a structured creative conversation. Each step file focuses on one domain (identity, vocal, emotions, personality, visual, validation), keeping context lean and questions focused. The wizard must validate completeness and present a review before writing the final bible.

Output: SKILL.md + 6 step files in `.claude/skills/create-artist/`
</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/02-artist-creation-wizard/02-RESEARCH.md
@.planning/phases/02-artist-creation-wizard/02-01-SUMMARY.md
@reference/templates/bible-template.md
@reference/suno/format.md
@reference/glossary.md
@artists/README.md
@CLAUDE.md
</context>

<tasks>

<task type="auto">
  <name>Task 1: Create SKILL.md wizard orchestrator</name>
  <files>.claude/skills/create-artist/SKILL.md</files>
  <action>
Create `.claude/skills/create-artist/SKILL.md` -- the main skill file that orchestrates the wizard flow.

Create directory path `.claude/skills/create-artist/steps/` first using `mkdir -p`.

**Frontmatter (YAML):**
```yaml
---
name: create-artist
description: Interactive wizard to create a complete virtual music artist identity. Use when the user wants to create a new artist, start the artist creation process, or build an artist bible from scratch. Guides through name, genre, vocal identity, emotion palette, themes, personality, lore, and visual keywords.
argument-hint: "[artist-name]"
---
```

Note: Do NOT include `disable-model-invocation` or `allowed-tools` -- these are not supported in Claude Code skill frontmatter. Only `name`, `description`, and `argument-hint` are valid fields.

**Body structure:**

1. **Title:** `# Create Artist Wizard`

2. **Persona section:** Remind Claude of its creative collaborator role (per CLAUDE.md). Speak French by default. Be enthusiastic, propose ideas, engage with the user's creative vision. Be specific in suggestions -- not generic placeholders.

3. **Arguments section:** `$ARGUMENTS` contains the artist name if provided. If empty, ask the user for the artist name as the first interaction.

4. **Process section:** Explain the step-by-step flow:
   - Work through each step sequentially
   - At each step: read the step file, present the domain with context and suggestions, wait for user input, summarize what was captured
   - Never ask all questions at once -- one domain per step
   - Target 2-4 questions per step to avoid wizard fatigue
   - Be conversational, not form-like -- offer rich suggestions the user can accept, modify, or reject

5. **Steps list:** Reference each step file:
   - Step 1: **Identite Musicale** -- Read `steps/01-identity.md`
   - Step 2: **Style Vocal** -- Read `steps/02-vocal.md`
   - Step 3: **Emotions et Themes** -- Read `steps/03-emotions-themes.md`
   - Step 4: **Personnalite et Lore** -- Read `steps/04-personality-lore.md`
   - Step 5: **Direction Visuelle** -- Read `steps/05-visual.md`
   - Step 6: **Revue et Validation** -- Read `steps/06-review-validate.md`

6. **Output section:** After validation in Step 6, write these files:
   - Create artist folder: `artists/[name-in-kebab-case]/`
   - Create bible: `artists/[name]/bible.md` using `reference/templates/bible-template.md` as structural schema
   - Create discography: `artists/[name]/discography.md` using `reference/templates/discography-template.md`
   - Create tracks directory: `artists/[name]/tracks/`
   - Write immediately once user approves in Step 6 (auto-save per CLAUDE.md -- no "are you sure?" dialog)

7. **References section:** List files Claude should consult:
   - Bible template: `reference/templates/bible-template.md`
   - Example bible: `.claude/skills/create-artist/examples/example-bible.md`
   - Genre/tag reference: `reference/suno/format.md`
   - Glossary: `reference/glossary.md`
   - Artist conventions: `artists/README.md`

8. **Rules section:** Key behavioral rules:
   - Never skip a step -- each step matters for a complete bible
   - Never generate content the user hasn't influenced -- always present options and let the user drive
   - The bible template structure is sacred -- fill it, don't reinvent it
   - Content can be explicit if it fits the artist's identity (per CLAUDE.md)
   - Step 6 is a review step, not a confirmation dialog -- present the bible, ask "Quelque chose a ajuster?", then write
  </action>
  <verify>
- `ls .claude/skills/create-artist/SKILL.md`
- Confirm frontmatter has name, description, argument-hint
- Confirm body references all 6 step files
- Confirm output section lists all 4 artifacts (bible, discography, tracks dir, artist folder)
- Confirm references section points to bible-template.md, example-bible.md, format.md, glossary.md, artists/README.md
  </verify>
  <done>SKILL.md exists with valid frontmatter, 6-step sequential flow, output instructions, and reference file list. A different Claude instance could execute this wizard without asking clarifying questions.</done>
</task>

<task type="auto">
  <name>Task 2: Create all 6 wizard step files</name>
  <files>.claude/skills/create-artist/steps/01-identity.md, .claude/skills/create-artist/steps/02-vocal.md, .claude/skills/create-artist/steps/03-emotions-themes.md, .claude/skills/create-artist/steps/04-personality-lore.md, .claude/skills/create-artist/steps/05-visual.md, .claude/skills/create-artist/steps/06-review-validate.md</files>
  <action>
Create 6 step files in `.claude/skills/create-artist/steps/`. Each step file follows this structure:
- Title (h1): `# Step N: [Domain Name]`
- `## Champs a Collecter` -- Obligatoires and Optionnels subsections
- `## Guidance pour Claude` -- How to present questions, what to suggest, references to consult
- `## Validation` -- Rules to check before moving to next step

**Step 01 - `01-identity.md` (Identite Musicale):**
- Obligatoires: Nom de scene (if not via $ARGUMENTS), genre principal (one dominant genre), sous-genres (1-3), langues (FR/EN/etc.), tempo range (BPM range)
- Optionnels: Age percu (apparent age)
- Guidance: Propose 3-5 genres based on user hints. Consult `reference/suno/format.md` for genre list. For each genre, suggest 2-3 natural subgenres. Ask about languages (min 1, max 3). Propose tempo range based on genre conventions.
- Validation: Genre must be recognized (present in format.md). At least one subgenre. At least one language. Tempo range coherent with genre.

**Step 02 - `02-vocal.md` (Style Vocal):**
- Obligatoires: Type de voix (timbre -- e.g., Female Airy Alto, Male Deep Baritone), style vocal (delivery -- e.g., Intimate, Aggressive, Smooth), techniques preferees (e.g., Whispered, Belted, Falsetto), registre (range)
- Optionnels: Tags Suno (pre-computed vocal tags for style prompts)
- Guidance: Reference `reference/suno/format.md` vocal delivery categories (8 categories). Propose vocal identity combinations that match the chosen genre. Suggest Suno tags derived from the vocal choices. Explain that Tags Suno will be used in future style prompts.
- Validation: Type de voix non vide. Style vocal non vide. At least one technique. Tags Suno suggested if not provided.

**Step 03 - `03-emotions-themes.md` (Emotions et Themes):**
- Obligatoires: Emotions primaires (3-5), themes recurrents (5-8), univers thematique (descriptive paragraph)
- Optionnels: Emotions secondaires (2-3), emotions interdites
- Guidance: Present emotions and themes as a SINGLE conversational step (not separately). Suggest emotions that naturally pair with the chosen genre. For themes, propose a thematic universe that connects them. Encourage defining "emotions interdites" -- explain this helps Phase 8 coherence engine prevent drift.
- Validation: At least 3 emotions primaires. At least 5 themes. Univers thematique is a paragraph (not a single word). Emotions primaires and interdites don't overlap.

**Step 04 - `04-personality-lore.md` (Personnalite et Lore):**
- Obligatoires: Traits de personnalite (2-3 phrases), bio publique (1-2 lines), tagline (short memorable phrase), lore/backstory (5-10 lines)
- Optionnels: Arc narratif (narrative trajectory for future tracks)
- Guidance: This is the most creative step. Offer to draft a lore based on everything collected so far. Bio publique should be a single sentence usable as a social media bio. Tagline should be quotable, memorable. Lore connects the artist's identity to their music -- why they create, what drives them.
- Validation: Personnalite is at least 2 sentences. Bio publique is max 2 lines. Tagline is one phrase. Lore is at least 5 lines and connects to the musical identity.

**Step 05 - `05-visual.md` (Direction Visuelle):**
- Obligatoires: Palette de couleurs (3-5 colors), style esthetique (one or two words), mots-cles visuels (5-10 keywords for AI image generation)
- Optionnels: Additional visual traits (clothing style, physical characteristics if relevant)
- Guidance: Note that visual generation is deferred to v2, but keywords are captured now for future use. Suggest colors and aesthetics that match the genre and emotional palette. Visual keywords should be usable in image generation prompts (Midjourney, DALL-E style keywords). This step can be brief -- 2-3 questions max.
- Validation: At least 3 colors. Style esthetique non vide. At least 5 visual keywords.

**Step 06 - `06-review-validate.md` (Revue et Validation):**
- This step is structurally different from steps 1-5. It doesn't collect new data -- it reviews and validates.
- `## Processus de Revue` section:
  1. **Completeness check:** List all critical fields. Flag any that are empty: nom, genre principal, sous-genres, type de voix, style vocal, emotions primaires, themes, personnalite, lore. If any are empty, loop back to the relevant step.
  2. **Consistency check:** Check for contradictions: genre vs. emotions (e.g., aggressive genre + only gentle emotions), vocal style vs. genre (e.g., whispered-only for heavy metal), tempo vs. genre. Flag contradictions with a brief explanation and ask if intentional.
  3. **Coherence preview:** Generate a brief "test scenario" -- describe how a hypothetical first track would use this bible (genre, vocal style, emotional tone, theme). This shows the user what the bible produces in practice.
  4. **Present the complete bible:** Format the entire bible exactly as it will be saved, using `reference/templates/bible-template.md` structure. Present it to the user.
  5. **Ask for adjustments:** "Quelque chose a ajuster?" If the user says no (or equivalent), proceed to write. If the user requests changes, revise the relevant sections and present again.
- `## Ecriture des Fichiers` section:
  - Once approved, write immediately (auto-save per CLAUDE.md):
    - `artists/[name-in-kebab-case]/bible.md`
    - `artists/[name-in-kebab-case]/discography.md` (from template)
    - Create `artists/[name-in-kebab-case]/tracks/` directory
  - Kebab-case conversion rules for artist name: lowercase, spaces to hyphens, remove special characters, accented characters kept as-is
  - Confirm to the user what was written and suggest next steps (e.g., "Vous pouvez maintenant creer un premier track avec /create-track [nom]")
- `## Champs Critiques` -- List of fields that MUST be non-empty: nom, genre principal, sous-genres (min 1), type de voix, style vocal, emotions primaires (min 3), themes (min 5), traits de personnalite, lore (min 5 lines)
  </action>
  <verify>
- `ls .claude/skills/create-artist/steps/` should show 6 files: 01-identity.md through 06-review-validate.md
- Each step file has h1 title, Champs a Collecter (except step 06), Guidance (except step 06), Validation sections
- Step 01 references reference/suno/format.md for genres
- Step 02 references reference/suno/format.md for vocal delivery categories
- Step 06 has Processus de Revue, Ecriture des Fichiers, Champs Critiques sections
- Step 06 references reference/templates/bible-template.md for output structure
  </verify>
  <done>All 6 step files exist with domain-specific questions, guidance, validation rules, and reference file pointers. Step 06 performs active validation (completeness + consistency + coherence preview) before writing. The wizard covers all fields required by the bible template.</done>
</task>

</tasks>

<verification>
1. `.claude/skills/create-artist/SKILL.md` exists with valid frontmatter and complete wizard flow
2. All 6 step files exist in `.claude/skills/create-artist/steps/`
3. SKILL.md references each step file by correct path
4. SKILL.md references bible-template.md, example-bible.md, format.md, glossary.md, artists/README.md
5. Step files cover all fields defined in bible-template.md (from Plan 02-01)
6. Step 06 validation covers all critical fields listed in phase success criteria
7. Step 06 writes to `artists/[name]/bible.md`, `discography.md`, and creates `tracks/` directory
8. No step asks all questions at once -- each focuses on one domain
</verification>

<success_criteria>
- The skill can be invoked and guides through 6 sequential steps
- Each step collects domain-specific identity data with suggestions and validation
- The wizard validates completeness and consistency before writing
- The user sees a complete bible preview before finalization
- Upon approval, the wizard writes bible.md, discography.md, and creates tracks/ directory
- All files reference the established project conventions and reference files
</success_criteria>

<output>
After completion, create `.planning/phases/02-artist-creation-wizard/02-02-SUMMARY.md`
</output>
