What problem does it solve? Teams often jump from a vague request straight into code or planning, which leads to wrong assumptions, missed constraints, and rework. This Skill forces a structured clarification phase that turns an initial request into a documented direction with separated facts, assumptions, and unknowns before any design or planning begins. ## Core Features & Use Cases - Forced step sequence: Seeds a DISCUSSION.md from a template, then walks through framing, spec quality review (feasibility, correctness, capability gaps), scope and options matrix, recommendation, and a self-check ledger. - Confirm-first clarification: Stops immediately on Critical or blocking issues, classifies the ask method (confirm, choice, fact, table, diagram, or HTML), and records questions and answers in a clarification checkpoint. - Optional visual decision aid: Generates an accessible VISUAL_DECISION.html with Tailwind and anime.js CDN tags for spatial or multi-state decisions, only after user confirmation. - Use Case: A stakeholder asks to add a search feature to an internal tool. The Skill seeds DISCUSSION.md, challenges the spec's feasibility against the repo, asks focused blocking questions, compares two implementation options, and hands off to the planning skill with a clear recommendation. ## Quick Start Ask the agent to use the brainstorming skill to clarify the goal, scope, and options for your feature request and produce a DISCUSSION.md before any planning.
