Game Design Feature Prioritization

Choose the strongest next move, not just the loudest idea.

Use this skill to compare candidate features or solution paths and decide what should happen now, later, or not at all. Keep the process practical. Rough structured judgment is better than fake precision, but explicit comparison is still useful.

Read references/family-conventions.md when you need the shared conventions for this GROW-derived skill family.

What to produce

Generate:

1. Candidate list - what is being prioritized
2. Evaluation matrix - impact, cost, fit, risk, timing
3. Priority ranking - now, later, discard, or monitor
4. Recommendation - what should happen next and why

Process