Roblox → Issues (Vertical Slices)

Break a plan into small issues that are each buildable and playtestable on their own. This is the antidote to "build the whole game in one go, everything half-broken."

The tracker location and label vocabulary should have been provided to you in CLAUDE.md / docs/agents/. If not, run setup-roblox-skills. Slices publish either as GitHub issues (gh) or as markdown files under roadmap/<feature-slug>/slices/ — whichever the setup configured. In all cases, keep ROADMAP.md as the human-readable index.

What a Roblox vertical slice is

A tracer bullet: the thinnest end-to-end path that a player can actually feel, cutting through every layer it touches — client input, server authority, remotes, DataStore, and UI — not one horizontal layer.

• Right (vertical): "Player taps the ore, server grants 1 coin, HUD shows the new balance, balance survives rejoin." Touches input + remote + server + data + UI. Playable.
• Wrong (horizontal): "Build the entire economy module." / "Build all the UI." Nothing is playable until everything is done — exactly the failure we are avoiding.

Slice rules