ChatGPT prompts for game development

Act as a senior game designer and technical design partner. Help me turn this concept into a small, buildable game design brief. Protect the player fantasy, but favor a clear core loop and testable decisions over a long feature list. Do not copy another game’s characters, story, art, dialogue, or proprietary design documents.

Game concept and player fantasy: [GAME CONCEPT]
Platform, engine, and team: [PLATFORM AND TEAM]
Target player and references: [AUDIENCE AND REFERENCES]
Constraints and intended scope: [SCOPE AND CONSTRAINTS]
What already exists: [CURRENT BUILD OR ASSETS]

Produce these sections:
1. A one-sentence high concept, player promise, genre, camera/control assumptions, and a 30-second player experience.
2. The core loop as a numbered cycle: player goal, action, feedback, reward, new decision, and repeat. Identify the main verb and the tension or tradeoff that makes repeated play interesting.
3. A minimum viable vertical slice with only the systems, content, UI, audio, art, and technical dependencies needed to prove the loop. Define what is explicitly out of scope.
4. Three linked systems tables: player actions and verbs; resources/progression/rewards; failure states and recovery. For each row, give rule, player-facing feedback, tuning variable, exploit risk, and implementation dependency.
5. A 10-minute playtest script with hypotheses, observation prompts, success criteria, and questions that avoid leading players.
6. A production backlog ordered by risk reduction, with owner role, estimate range, dependency, and acceptance criteria. Include accessibility basics such as remapping, readable text, motion sensitivity, and audio/visual cues where relevant.

Flag feature creep, unclear win conditions, loops that lack meaningful choices, and references that are too close to copy. Before finalizing, check that every proposed feature supports the stated player promise and that the vertical slice can be tested without building the full game. Ask up to 3 clarifying questions only if a required input is missing.

Audit the core loop of my game prototype. Concept: [CONCEPT]. Current player actions: [CURRENT LOOP]. Playtest observations: [PLAYTEST NOTES]. Intended player feeling: [PLAYER PROMISE]. Identify where the loop lacks a decision, clear feedback, tension, reward, or reason to repeat. Propose three small experiments, each with one changed rule, predicted player behavior, instrumentation or observation, and a pass/fail threshold. Preserve the stated player promise and avoid adding new major systems. Flag assumptions not supported by playtest evidence. Ask up to 3 questions only if required information is missing.

Design one playable quest for [GAME AND PLAYER ROLE] that introduces or tests [MECHANIC]. The player context is [CURRENT STATE], intended duration is [DURATION], and production limits are [ASSETS AND CONSTRAINTS]. Produce beats for setup, objective, obstacle, player choice, feedback, resolution, and reward; include failure and recovery paths, required assets, dialogue purpose rather than full script, and acceptance criteria. Ensure the quest teaches through play rather than an exposition dump. Do not copy plot or characters from references. Ask up to 3 questions only if necessary.

Create a moderated playtest plan for [GAME BUILD] with [TARGET PLAYERS]. The features being tested are [FEATURES], and our uncertain design questions are [HYPOTHESES]. Produce a 45-minute session guide: consent and context, tasks in order, neutral moderator prompts, observations to record, event metrics, post-test questions, and a results template. Include instructions not to teach the player unless the test specifically measures onboarding. Define what result would cause us to revise each feature. Ask up to 3 questions only if required details are missing.