Gsp Concept Brainstorm
Use when a game idea is still vague and needs pillars, verbs, and an acceptance bar before implementation.
Install
$ agentstack add skill-mike007jd-game-superpowers-gsp-concept-brainstorm ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-mike007jd-game-superpowers-gsp-concept-brainstorm) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Game Concept Brainstorm
Goal
Lock the game fantasy before architecture or implementation.
Outputs
Follow the gsp-orchestrator output strategy:
- inline (default): present concept brainstorm and requirements in conversation.
- minimal or full: write
docs/game-studio/concept-brainstorm.mdanddocs/game-studio/requirements.md.
Use ./shared/templates/concept-brainstorm.md.
Workflow
- Restate the player fantasy in one sentence.
- Lock the primary verb, the reward loop, and the first 30-second promise.
- Lock the game shape before coding: camera / view model, movement grammar, obstacle or encounter grammar, fail / retry rhythm, and visual anchor.
- Define 3-4 design pillars.
- Separate must-haves from experiments.
- Ask enough high-value questions to remove shape ambiguity. Good question types: subtype, references, control grammar, failure rhythm, visual anchor, and “what must beat baseline.”
- For benchmark or one-prompt builds, spend more tokens here than feels comfortable if ambiguity remains.
- Feed the result into
gsp-requirements-brainstorm,gsp-scope-profile, andgsp-ux-flow-designer.
Important
If the prompt uses an archetype word that can imply multiple valid game forms, do not silently choose one and move on. Examples: runner, shooter, breakout. Write the chosen interpretation explicitly so downstream skills inherit a locked shape instead of improvising. Do not optimize for asking fewer questions. Optimize for asking the fewest questions that still fully lock the concept.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: mike007jd
- Source: mike007jd/game-superpowers
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.