Plan small, playable Rust game implementation slices from a short design brief, MVP, stretch goals, and acceptance checks.
SkillScore73Maintained
Automatic
◆Coding pack
Last verified 8/16/2026
What it changes
Passed 16 of 22 test cases with the skill, and 11 of 22 without it.
Without skill50%
With skill73%
Checks it passed that the model alone missed
Focuses the MVP slice strictly on basic tile interactions and crop planting
Restricts the first slice to the baseline click mechanic and incrementing counter
Restricts Milestone 1 to the smallest single-player or local playable interaction loop
and 5 more in the full report
6 fixed10 passed either way5 still failing1 broke
Pass-rate lift
+23 pp
Tokens
-19%
Agent turns
0%
Response time
-25%
Model gemini-3.6-flashMeasured 8/16/2026v116 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
I'm starting a 2D space shooter in Rust using Macroquad. I need help breaking down my raw concept into incremental implementation steps. Please structure a project plan that isolates the minimal viable gameplay loop, outlines ordered playable slices, and includes local verification criteria for each milestone.
What was checked, without and with the skill
Checked
Without skill
With skill
Includes a design brief section containing a title, short description, core loop, MVP, stretch goals, technical constraints, and target controls
Missed
Passed
Structures each development slice so that it delivers one visible player-facing capability
Passed
Passed
Provides local verification checks for each implementation slice
Passed
Passed
case-01 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md28 lines2 files
Rust Game Slice Planning
Use this skill to turn a Rust game idea into small, playable implementation
slices. Optimize for visible progress, limited scope, and an MVP that can be
finished before optional polish work begins.
Core Workflow
Write or recover a short design brief: title, short description, core loop,
MVP, stretch goals, technical constraints, and target controls.
Separate "must ship" mechanics from stretch goals. Keep the first milestone
to the smallest playable loop.
Convert the MVP into ordered slices. Each slice should compile, run, and add
one visible player-facing capability.
Give each slice acceptance checks that an agent can verify locally.
Defer content expansion, visuals, extra systems, and balance work until the
current slice is complete.
Read Next
Read references/slice-planning.md for the design brief template, slice order,
and anti-overbuilding checks.
Source Notes
Guidance is transformed and paraphrased from Herbert Wolverson's Hands-On
Rust, especially Chapter 4 and Appendix A2, and from the official companion
source repository. This is not official material from the author or publisher.