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.
1---2name: rust-game-slice-planning3description: Plan small, playable Rust game implementation slices from a short design brief, MVP, stretch goals, and acceptance checks. Use when starting a Rust game, scoping a prototype, converting a game idea into work items, or preventing an AI coding agent from overbuilding.4license: MIT5compatibility: Codex, Claude Code, and other Agent Skills-compatible clients.6metadata:7 version: "0.1.0"8 displayName: Rust Game Slice Planning9 category: Rust10 tags: rust,gamedev,planning,mvp,scope11---1213# Rust Game Slice Planning1415Use this skill to turn a Rust game idea into small, playable implementation16slices. Optimize for visible progress, limited scope, and an MVP that can be17finished before optional polish work begins.1819## Core Workflow20211. Write or recover a short design brief: title, short description, core loop,22 MVP, stretch goals, technical constraints, and target controls.232. Separate "must ship" mechanics from stretch goals. Keep the first milestone24 to the smallest playable loop.253. Convert the MVP into ordered slices. Each slice should compile, run, and add26 one visible player-facing capability.274. Give each slice acceptance checks that an agent can verify locally.285. Defer content expansion, visuals, extra systems, and balance work until the29 current slice is complete.3031## Read Next3233Read `references/slice-planning.md` for the design brief template, slice order,34and anti-overbuilding checks.3536## Source Notes3738Guidance is transformed and paraphrased from Herbert Wolverson's *Hands-On39Rust*, especially Chapter 4 and Appendix A2, and from the official companion40source repository. This is not official material from the author or publisher.
ConcertoNotes