Goal
Turn a Roblox idea into a shippable, updateable game plan that protects retention and avoids premature polish.
Roadmap Discipline
- Read project roadmap and instruction files before choosing work.
- Resume from the first unchecked item unless the user redirects.
- Mark an item complete only after implementation, testing/playtesting, and explicit human approval.
- Use an awaiting-approval marker for work that is built and tested but not approved.
- Keep current-state notes in sync with what was actually shipped.
First Week Design
- Day 1: immediate fun, clear loop, first reward, first goal.
- Day 2: daily streak, unfinished objective, or friend/social reason to return.
- Day 3: unlock meaningful new content around 2-3 hours of play.
- Days 4-6: visible medium-term goals, collection progress, social identity.
- Day 7: advertised reward or milestone visible from Day 1.
Update Cadence
Plan updates around:
- New zones, modes, enemies, quests, pets, cosmetics, or upgrades.
- Limited events and seasonal items.
- Balance changes driven by funnel and retention data.
- Social goals that encourage friends to return together.
Task Sequencing
Prioritize:
- Core action and reward loop.
- Progression signals and save/load.
- Social and return hooks.
- Mobile UX and performance.
- Monetization that fits the loop.
- Content expansion and live events.
Output Format
For roadmap work, provide:
- Current phase.
- Next buildable milestone.
- Acceptance criteria.
- Playtest criteria.
- Approval gate.
- Risks to retention, monetization fairness, or mobile performance.
Next
Break the roadmap into playtestable slices with roblox-to-issues, and ship each update through roblox-release-operations.