Roblox → PRD

Turn what is already decided into a concise, buildable game design brief (PRD). Do NOT interview the user from scratch — synthesize the concept, conversation, and place state you already have. If the concept has not been pressure-tested yet, run roblox-game-ideas (grilling mode) first.

The tracker location and label vocabulary should have been provided to you in CLAUDE.md / docs/agents/. If not, run setup-roblox-skills.

Why this exists

The single biggest failure mode in AI-built Roblox games is trying to build the whole game in one pass, which leaves everything half-working. A PRD is the contract that a later step (roblox-to-issues) slices into small, independently playtestable pieces. Keep it tight: enough to slice, not a novel.

Process

1. Read the current state. Connect through roblox-studio-workflow if a place exists. Read ROADMAP.md if present. Use the game's own vocabulary consistently (currency names, entity names, zone names).

2. Sketch the systems, not the whole game. List the major server-authoritative systems and client controllers this concept needs (core loop, economy, save/load, progression, social, UI surfaces). Flag which hold valuable state (currency, inventory, purchases, rewards, progression) — those must be server-authoritative. Confirm the system list matches the user's expectation before writing.

3. Handle UI up front. If the concept has meaningful UI, note whether a Roblox UI design artifact exists yet (see roblox-game-ux). If not, record an explicit design step rather than treating UI as ready to build.

4. Write the PRD using the template, then publish it to the tracker with the needs-triage label/status so it enters the normal flow.