roblox-triage

Roblox Triage

Move slices and bug reports through a small state machine so that anything marked "ready to build" is actually specified enough to build in one focused pass — and playtestable when done.

The tracker location and label vocabulary should have been provided to you in CLAUDE.md / docs/agents/. If not, run setup-roblox-skills. If the tracker is GitHub, prefix any AI-written comment with > *Generated by AI during triage.*.

Reference

• BUILD-BRIEF.md — how to write a durable build brief for a ready-to-build slice.

Roles

Two category roles:

• bug — something is broken in the place.
• enhancement — a new slice / capability.

Five state roles:

• needs-triage — not yet evaluated.
• needs-info — waiting on the user for a decision or detail.
• ready-to-build — fully specified; an agent can build it in one pass with no missing context.
• needs-human — needs the user (a Studio action, a design call, a balance judgment, a purchase test).
• wontfix — will not be actioned.

Every triaged item carries exactly one category and one state role. These are canonical names; the actual label/status strings are in docs/agents/triage-labels.md.

Normal flow: needs-triage → (needs-info ↔ needs-triage) → ready-to-build / needs-human / wontfix. The user can override; flag anything unusual and ask first.

UI design gate

A slice that changes user-facing UI cannot become ready-to-build until an approved Roblox UI design artifact exists for it (see roblox-game-ux for what that artifact contains: layout, states, and mobile/tablet/desktop behavior, marked Status: approved). If it is missing or still draft, the slice becomes needs-human with a note that it needs the UI design step first.

Invocation

The user invokes this in natural language: "what should we build next?", "triage this bug", "is this slice ready?", "mark the coin-pickup slice ready to build". Interpret and act.

Show what needs attention

Present three buckets, oldest first: untriaged, needs-triage, and needs-info with new user input. Show a one-line summary each and let the user pick.

Triage one item

1. Gather context. Read the item fully (and prior triage notes so you don't re-ask). Connect via roblox-studio-workflow and inspect the relevant scripts/instances. For UI items, check the design artifact.
2. Recommend. State your category + state recommendation with reasoning and a short summary of the relevant place state. Wait for direction.
3. Reproduce (bugs only). Before anything else, try to reproduce in a Studio playtest and read get_console_output. A confirmed repro (with the failing code path) makes a far stronger build brief; no repro is a strong needs-info signal. Hand hard bugs to roblox-debugging-bugfix.
4. Sharpen (if needed). If the item is vague, run a short grilling pass (see roblox-game-ideas grilling mode) to pin down the decision.
5. Apply the outcome:
   • ready-to-build — post a build brief (BUILD-BRIEF.md). For UI, include the approved artifact path.
   • needs-human — same structure, but say why it can't be delegated.
   • needs-info — post triage notes: what's established, and the specific questions still open.
   • wontfix — brief reason; for enhancements, note why so it isn't re-suggested.

Quick override

If the user says "mark X ready to build", trust them and apply it after checking for conflicting state roles and the UI design gate. If a UI artifact is missing, say exactly what's missing and ask for explicit override before applying ready-to-build.

Next

Build the ready-to-build slice with its phase specialist (roblox-luau-architecture, roblox-combat-systems, roblox-ui-implementation, roblox-datastore-persistence, etc.), then verify with roblox-playtest-qa and roblox-mobile-playtest. If a bug was triaged, hand it to roblox-debugging-bugfix. Return to roblox-game-development-lifecycle to pick the next slice.