Skip to content
Back to skills

Game Planning

ASecurity

Use when defining a game's smallest playable slice, limiting feature scope or deciding whether a proposed loop has a meaningful player outcome.

  • 11 stars
  • 0 votes
  • 1 copy
  • 2 views
  • Added October 23, 2026
ai-agentsgo

Works with

  • cli

Security analysis

A100/100

Scanned October 23, 2026

npx -y skills add jammyfu/open-game-skills --skill game-planning --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Game Planning?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Game Planning
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jammyfu-game-planning/badge)](https://www.skillsdirectory.com/skills/jammyfu-game-planning)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: game-planning
description: Use when defining a game's smallest playable slice, limiting feature scope or deciding whether a proposed loop has a meaningful player outcome.
---

# Game planning

Record existing genre, target device, input roles and selected modes before expansion. Keep the slice small enough to validate; do not add combat, locomotion, loot or progression merely to satisfy an action-game template.

## Slice contract

Publish:
- stable `slice_id` and `slice_revision`
- pillars and explicit scope exclusions
- target/device/input context
- core challenge or decision
- start and end conditions
- failure/retry or explicit no-failure policy
- dependent skill modes/versions
- acceptance evidence and untested remainder
- next milestone and exit criteria

The player understands the goal, completes one **core challenge or decision**, perceives its consequence, and knows what to do next. Combat is one possible loop; noncombat games are equally valid.

| Loop | Core challenge | Observable consequence |
|---|---|---|
| combat | win or survive an encounter | outcome and next opportunity |
| puzzle | solve with taught properties | changed room or new possibility |
| building/simulation | build or allocate a limited resource | visible system response |
| narrative | make an informed choice | acknowledged consequence or branch |
| rhythm/racing | finish a passage or lap | timing/line feedback and retry |

## Rules

1. Revisions change when scope, goal, acceptance or dependent modes materially change.
2. Evidence must name the exact slice/build/revision; a demo clip or debug setup cannot silently stand in for a natural clear.
3. Stabilize only the systems used by this slice before expanding content volume.
4. Preserve project facts and prior choices; ask only for consequential missing decisions.

## Acceptance

`gameplay-validation` can run the natural start-to-outcome chain against the published `slice_id`/revision and return pass/fail/blocked/not-run with evidence. Expansion follows demonstrated slice goals, not a genre checklist.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.