# Gsp Requirements Brainstorm

> Use when a game request is vague, contradictory, or under-specified and needs a production-ready brief.

- Skill: `mike007jd/gsp-requirements-brainstorm-2` (Agent Skill, multi-file: 8 files)
- Install (CLI): `npx skillmds@latest add mike007jd/gsp-requirements-brainstorm-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mike007jd/gsp-requirements-brainstorm-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: mike007jd (https://skillmd.com/u/mike007jd)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mike007jd/gsp-requirements-brainstorm-2

---


# 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.md` and `docs/game-studio/quality-target.md`.

Use:
- `./shared/templates/requirements-brief.md`
- `./shared/templates/quality-target.md`

## Workflow
1. Extract what the user definitely wants.
2. Separate must-build features, must-not-cut qualities, optional features, and explicit non-goals.
3. Infer smart defaults when they are obvious.
4. Ask high-value clarifying questions whenever missing information would materially affect game form, feature correctness, wow-factor, UX / onboarding, audio / feedback, or verification standards.
5. Do not stop after one question if multiple unresolved details still meaningfully change the result.
6. Write acceptance tests in user language.
7. Decide whether the quality target should be `first-playable`, `polished-prototype`, `production-feature`, or `live-patch`.

## Important
For greenfield showcase work, do not reduce the ask to a bare minimum.
Default to high-precision questioning rather than question minimization.