Gsp Requirements Brainstorm
Use when a game request is vague, contradictory, or under-specified and needs a production-ready brief.
Install
$ agentstack add skill-mike007jd-game-superpowers-gsp-requirements-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-requirements-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 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.
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.