Give each person one design job
Set a short round where one person names the player action, another proposes the goal, and a third identifies a fair failure or restart rule. Write each option on a card, then vote on one coherent combination. When two ideas conflict, keep the one that lets a tester understand the outcome from the screen.
Use a workshop brief everyone can inspect
Example brief: “Make a one-screen cooperative-feeling puzzle for a single player: rotate a shared bridge to guide three colored tokens into matching gates. Each token moves one tile after a rotation. A token hitting a closed gate resets that attempt; reaching all three gates completes the puzzle. Restart restores the same bridge and tokens.” The phrase cooperative-feeling describes a shared planning mood, not a live multiplayer feature. Read the draft aloud and remove rules nobody can explain.
Test the group decision
Choose one person who did not help write the brief to play the first version. Ask what they thought would happen before each move, then compare those predictions with the result. Give the group one revision round focused on the largest mismatch, not a new list of everyone's favorite additions.
Record who owns the prompt and how the public result will be shared before generation. If the workshop needs multiple people editing one document at the same time, use your usual shared notes tool for the discussion and treat this product as the later single-author generation step.
Questions about collaborative game prompt workshop
How many people should contribute to the first prompt?
A small group can give each person a concrete role and still reach a decision. With a larger group, gather ideas first, then have a smaller design pair combine and read back the rules.
What if the group wants two incompatible mechanics?
Keep them as separate one-sentence concepts and choose one for the first prototype. A focused test can show which rule deserves another iteration without forcing both into one confusing build.