ush-game-meeting-plan

What problem does it solve? Game development teams generate meeting notes, chat transcripts, and decision logs that mix approved decisions with open discussion, rejected ideas, and unverified claims. Turning that raw evidence into an actionable plan without inventing consensus or contradicting prior decisions is error-prone and time-consuming. ## Core Features & Use Cases - Evidence Classification: Sorts every item from meeting notes or chat exports into explicit decisions, action items, discussion, rejected options, hypotheses, and blockers. - Consensus Discipline: Refuses to treat silence, reaction counts, or repeated discussion as approval, and flags missing or conflicting evidence as risks instead of guessing. - Read-Only Planning: Produces an ordered implementation plan with verification steps and risks, optionally cross-checked against the repository, without editing any files. - Use Case: After a game design meeting, paste the transcript and ask for a scoped implementation plan; the output separates what was actually decided from what was merely discussed, with concrete next steps and open questions. ## Quick Start Turn these game design meeting notes into a scoped implementation plan with priorities, verification steps, and open risks.