create-midi

> STOP. READ THIS ENTIRE SKILL.MD BEFORE CALLING ANY ENDPOINT. # /create-midi Two capabilities in one skill: ## 1. Compose Arrangement (`compose`) LLM creates a full multi-track arrangement given: - **Annotated lyrics** (S04 output) — vocal melody timing, syllable stress - **MIDI fragments** (from /consume-midi) — reference bass lines, drum patterns, chord voicings - **Arrangement notes** (from S02) — natural language description of reference song structure - **Heart tags** (from S00) — emotional dynamics per section (anger→sadness→fear) ```bash ./run.sh compose \ --lyrics annotated-lyrics.json \ --references consume_midi_results.json \ --arrangement arrangement_notes.md \ --heart "anger,sadness,fear" \ --out piano-roll-spec.json ``` **Prompt managed by /prompt-lab** — the composition prompt needs to understand: - Chord voicings and voice leading - Bass line patterns (root, fifth, walking, pedal) - Drum grooves (kick/snare/hihat patterns per feel) - Counter-melody construction - Energy curve shaping (build, drop, sustain) - How heart tags translate to musical choices (fear = sparse, anger = driving, sadness = sustained) Output: `piano-roll-spec.json` with notes for vocal, bass, drums, keys, guitar, synth. ## 2. Convert (`from-spec`, `to-spec`) Mechanical JSON↔MIDI conversion via pretty_midi. No LLM involved. ```bash # JSON → MIDI (compile the arrangement to playable file) ./run.sh from-spec --spec piano-roll-spec.json --out arrangement.mid # MIDI → JSON (import existing MIDI for analysis or editing) ./run.sh to-spec --midi input.mid --out spec.json ``` The MIDI file has separate tracks per instrument. This is the song's intermediate representation — between creative decisions and audio rendering. ## 3. Battle Score Packet Validation (`validate-score-packet`) Deterministically validate `battle.music_score_packet.v1` packets for the Battle Music Director subagent. This command is validation-only: it does not render MIDI, play audio, schedule playback, or promote a score. ```bash ./run.sh validate-score-packet \ --packet battle.music_score_packet.v1.json \ --motif-manifest battle_music_manifest.json \ --out validation.json ``` The validator checks: - required score packet fields; - receipt binding shape; - future bar/beat boundary shape; - tempo, meter, intensity, and motif role bounds; - optional motif existence against a supplied manifest; - raw path redaction boundaries; - unsupported Battle outcome claims. Claim boundary: ```text mocked: false live: local_deterministic_validator proves: score-packet structure is valid for deterministic handoff does_not_prove: MIDI rendering, audio playback, Battle promotion, victory, death, exploit success, Blue outcome, or Judge success ``` ## Architecture Note `midi_utils.py` was originally in `/create-music`. It moved here because arrangement composition is a distinct creative step, not a sub-feature of audio generation.