rpg-soundscape-forge

RPG Soundscape Forge — soundtrack manifest → Foundry playlists + scene ambience

What this skill is for

Turn the campaign's soundtrack manifest (soundtrack-manifest-<slug>.md, authored by rpg-sound-director) into live Foundry audio. You do not choose the music or generate it — the manifest names the track, mood/function, file path, and how to bind it. You realize it: create the Playlist, bind it to the right scene's Ambience, place AmbientSound cues, record the ids. If audio files or the MCP audio tools are missing, you degrade and report — you never invent a track. This is the audio analogue of rpg-scene-forge.

Workflow

1. Read the manifest — soundtrack-manifest-<slug>.md (vault/working root). Each row gives: scene/local, function, provider, expected filename, Data-relative path, loop, volume, bind-as (scene playlist | AmbientSound (one-shot)). This is the contract; you don't re-derive moods from prose.
2. Confirm files are placed. The audio files must already be in the Foundry data dir at their Data-relative path (worlds/<world>/audio/<name>.ogg). There is no MCP file-stat tool — ask the GM to confirm the generated files are dropped in, or proceed and flag that a wrong/absent path yields a silent track. Never bind a remote URL.
3. Resolve the scene. Match the manifest's scene/local name to a Foundry scene via list-scenes (when run standalone), or take the sceneId handed down by rpg-scene-forge (when run by the conductor, right after the scene is built). Surface any unmatched scene as a blocker — don't guess.
4. Prefer existing. list-playlists and match by name before creating, so re-runs don't duplicate (idempotency — mirror scene-forge's link-existing rule).
5. Create the playlist (for bind-as: scene playlist) — create-playlist({ name, mode, fade, sounds:[{ path, volume, loop, fade, channel }] }). Pass each track's channel (music/environment/interface) from the manifest's Channel column — for a layered simultaneous bed, split music vs ambience across channels so the GM gets independent live faders (references/soundscape-policy.md). One playlist per scene, or one campaign-ambience playlist with per-scene tracks (judgment — same reference).
6. Bind to the scene — set-scene-playlist({ sceneId, playlistId, soundId? }). The scene's Ambience auto-plays the playlist on activation.
7. Place one-shots (for bind-as: AmbientSound (one-shot)) — create-ambient-sound({ sounds:[{ path, x, y, radius, volume, repeat:false }] }) for a localized/triggered cue (a bard's song, a fountain, a reveal stinger). Placement coords are judgment.
8. Serialize. All audio writes to ONE scene happen as a single sequential batch — never parallel (the 2nd write silently no-ops; the load-bearing forge rule).
9. Approval-gate + record. Confirm the bind plan with the GM before writing (which playlist → which scene). Return { playlistId, soundIds, sceneBound } to the conductor for the build manifest.