Gsp playability verifier

Skill mike007jd/game-superpowers/skills/gsp-playability-verifier

Skills-first game development superpowers for Claude Code and Codex: build, audit, polish, and productionize game projects with reusable Agent Skills.

Install

npx -y skills add mike007jd/game-superpowers --skill gsp-playability-verifier

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when verifying a game build against its quality target before claiming it is complete.

SKILL.md

1.8 KB, as published. Nobody here has run it

Game Playability Verifier

Goal

Verify the build against its actual target, not a generic low bar.

Outputs

Follow the gsp-orchestrator output strategy:

inline (default): present verification results in conversation.
minimal or full: write docs/game-studio/quality-report.md.

Use

../../shared/templates/quality-report.md
../../shared/checklists/first-playable-rubric.md
../../shared/checklists/polished-prototype-rubric.md
../../shared/checklists/playability-verifier-output-checklist.md
../../shared/checklists/ui-ux-hard-rules.md

Quality-aware verification

If the target is first-playable, use ../../shared/checklists/first-playable-rubric.md.
If the target is polished-prototype, also use ../../shared/checklists/polished-prototype-rubric.md.
If the target is production-feature or live-patch, verify the requested feature set plus regression risk in touched areas.

Minimum checks

boots
reaches the correct actionable state
requested verbs work
requested critical features in scope are present
HUD / affordances are readable
playfield is not obviously sacrificed to UI clutter
no blocking runtime errors
the build quality matches the selected target

Reporting rules

For each critical check, report:

pass / fail / partial
evidence source
short note or repair direction

Important

Do not declare success merely because something runs. The verifier exists to catch “technically alive, product-wise weak” outcomes. When runtime evidence is missing, say so explicitly. In a multi-agent build flow, this skill is the default verifier stage after implementation review, not an optional final flourish.