ashexplained/roblox-skills

roblox-liveops-roadmap

Plan Roblox live ops, update cadence, event systems, retention milestones, roadmap checkboxes, approval gates, content pacing, Day-1/Day-3/Day-7 hooks, quests, rewards, and release-ready task sequencing.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/ashexplained/roblox-skills --skill roblox-liveops-roadmap

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Roblox Live Ops Roadmap

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:

  1. Core action and reward loop.
  2. Progression signals and save/load.
  3. Social and return hooks.
  4. Mobile UX and performance.
  5. Monetization that fits the loop.
  6. 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.

from this repository

More skills

All skills
ashexplained
Community

roblox-playtest-qa

Playtest Roblox experiences through Studio MCP with attention to first-session fun, mobile UX, console errors, progression, social hooks, performance, and exploit-sensitive flows.

1h installs
4
GitHub stars
63
Updated
Jul 1
ashexplained
Community

roblox-animation-audio-feedback

Improve Roblox feel through animation, audio, VFX, haptics-like feedback, reward juice, movement feel, combat feedback, UI transitions, emotes, and satisfying loop feedback without hurting mobile performance.

1h installs
3
GitHub stars
63
Updated
Jul 1
ashexplained
Community

roblox-combat-systems

Design, implement, and review Roblox combat systems. Use for melee, ranged, abilities, cooldowns, hit detection, damage validation, status effects, enemy AI hooks, combat UI, balance knobs, VFX/SFX, and exploit-resistant remotes.

1h installs
3
GitHub stars
63
Updated
Jul 1
ashexplained
Community

roblox-creator-store-security-audit

Audit Roblox Creator Store, Toolbox, inventory, group, universe, package, model, UI, gameplay, plugin-like, and other third-party imported assets for malicious or risky scripts. Use whenever Claude imports, inserts, reviews, or trusts Creator Store assets, especially assets with Scripts, LocalScripts, ModuleScripts, hidden descendants, require calls, HTTP, DataStore, remote creation, obfuscated code, or suspicious names.

1h installs
3
GitHub stars
63
Updated
Jul 1