Playtest Feedback to Iteration Plan

The Prompt

You are a pragmatic playtest analyst. Turn this prototype feedback into a ranked iteration plan.

PROTOTYPE GOAL:
{{prototype_goal}}

PLAYTEST NOTES:
{{playtest_notes}}

OBSERVED PLAYER BEHAVIOR:
{{observed_behavior}}

KNOWN BUGS:
{{known_bugs}}

TIME BUDGET:
{{time_budget}}

NON-GOALS:
{{non_goals}}

Return exactly these sections:

1. What Players Understood
2. What Players Missed
3. Core Loop Health
4. Critical Fixes Before New Features
5. Cheap Improvements
6. Ideas To Ignore For This Prototype
7. Next Build Task Brief
8. Stop / Pivot / Continue Recommendation

Rules:
- Separate player confusion from bugs.
- Do not recommend adding content to mask a weak core loop.
- Prefer changes that improve readability, control, feedback, restart, or goal clarity.
- Respect the stated non-goals and time budget.

When to Use

Use this after the first playable pass. It is designed for messy notes from friends, teammates, students, or a tiny internal playtest. The point is to avoid treating every comment as a feature request.

This prompt works well when the prototype is still rough: colored shapes, draft sprites, placeholder audio, incomplete balancing, and one loop that needs honest feedback.

Variables

Variable	Description	Example
prototype_goal	What the prototype was meant to prove	”test whether sorting under time pressure feels satisfying”
playtest_notes	Raw tester comments	”I did not see the timer; restart was fun; controls felt slippery”
observed_behavior	What players actually did	”two testers ignored the blue lane for the first 30 seconds”
known_bugs	Issues already identified	”score sometimes increments twice”
time_budget	Available iteration time	”90 minutes”
non_goals	Work that should stay out	”no new art pass, no extra levels”

Tips & Variations

• Add screenshots or short clips if the model supports multimodal input.
• Ask for a “one-hour patch plan” when the prototype is for a game jam.
• Ask for a separate “kill criteria” section if the team is too attached to the idea.
• For public prototypes, add a rights and attribution review before shipping generated assets.

Example Output

• Critical fix: make the objective visible before the first action.
• Cheap improvement: add hit feedback and a restart key hint.
• Ignore: new enemy types, upgrade shop, story intro.
• Recommendation: continue for one more loop only if the next build improves readability without adding systems.

Related site references

• Use Case: AI-Assisted Game Prototype Sprint
• Prompt: Output Quality Evaluator and Follow-Up Questions
• Model: Claude Sonnet
• Model: GPT