Build Planner

Inputs

• Episode strategy: viewer promise, final demo sketch, complexity intuition.
• Optional: existing workspace/playground/<slug>/ if the build already started.

Process

1. Identify the smallest set of features that can deliver the final demo. Anything not strictly required → "leave for episode 2".
2. Pick a stack. Default to browser-first (HTML/CSS/JS or React + Tone.js + Web Audio API) for the first 10 episodes. See references/stack-defaults.md.
3. Decompose into 3–6 build milestones, each finishable in a single Claude Code session.
4. Identify risk areas — see references/risk-checklist.md. Common: audio scheduling, browser autoplay gating, MIDI permissions, latency.
5. List explicit out-of-scope items.

Outputs

workspace/playground/<build>/build-notes.md with sections: