Little Game Planning Master

Problem

Planning lightweight mini-game demos often fails in two ways. A one-sentence idea may jump straight into code, leaving levels, story, and assets disconnected. Or the design doc stays too vague for an AI coder to implement a playable H5 or WeChat mini-game. This skill turns planning into a checkable workflow, aiming to produce detailed, implementable design documents.

How it works

The skill follows four phases:

• Clarify requirements: ask a limited number of questions to turn the user’s idea into a game overview, core experience, gameplay framework, narrative style, and special needs.
• Concept design: use progressive disclosure to read references step by step and produce conclusions, instead of dumping all design elements at once.
• Document implementation: generate overall planning, level design, content design, and asset list; add an AI logic document when the demo requires AI-driven behavior.
• Self-review: check the outputs against a checklist and fix missing level goals, story triggers, or asset gaps.

It keeps scope to 10-15 levels, requires a complete story ending, and defaults to a pure frontend approach, making it suitable for demos that can be picked up within about 10 minutes.