Gsp requirements brainstorm
Skill mike007jd/game-superpowers/publish/clawhub/gsp-requirements-brainstorm
Use when a game request is vague, contradictory, or under-specified and needs a production-ready brief.From its SKILL.md
npx -y skills add mike007jd/game-superpowers --skill gsp-requirements-brainstormAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.4 KB, 278 tokens by cl100k_base, as published. Nobody here has run it
Game Requirements Brainstorm
Goal
Turn the request into a requirement set that is specific enough to build a strong result.
Outputs
Follow the gsp-orchestrator output strategy:
- inline (default): present requirements and quality target in conversation.
- minimal or full: write
docs/game-studio/requirements.mdanddocs/game-studio/quality-target.md.
Use:
./shared/templates/requirements-brief.md./shared/templates/quality-target.md
Workflow
- Extract what the user definitely wants.
- Separate must-build features, must-not-cut qualities, optional features, and explicit non-goals.
- Infer smart defaults when they are obvious.
- Ask high-value clarifying questions whenever missing information would materially affect game form, feature correctness, wow-factor, UX / onboarding, audio / feedback, or verification standards.
- Do not stop after one question if multiple unresolved details still meaningfully change the result.
- Write acceptance tests in user language.
- Decide whether the quality target should be
first-playable,polished-prototype,production-feature, orlive-patch.
Important
For greenfield showcase work, do not reduce the ask to a bare minimum. Default to high-precision questioning rather than question minimization.
What ships with it: 7 files
5.2 KB alongside SKILL.md
examples/
- usage.md645 B
shared/
tests/
- smoke.md465 B
- CHANGELOG.md216 B
- MANIFEST.yaml2.2 KB
- README.md1.0 KB