requirements-elicitationlisted

# Requirements Elicitation — From Vague Brief to Clear Spec ## What This Skill Does This skill runs a **structured elicitation process** that transforms a rough idea or vague brief into a concrete set of requirements. It surfaces assumptions, identifies gaps, forces prioritisation, and produces a document the user can hand to a team or use as a project foundation. It is not a template filler — it's an interactive process that asks targeted questions to draw out what the user knows (and doesn't know they know) about what they want to build. ## When to Use This Skill Use when: - The user has a project idea but hasn't formalised requirements - A brief or PRD exists but feels incomplete or hand-wavy - The user is about to start building and wants to think it through first - Someone says "I want to build X" without specifying what X actually does Do NOT use when: - Requirements already exist and the user wants to implement them - The user wants architecture or design decisions (use tree-of-thought or graph-of-thought) - The task is a small, well-defined piece of work (just do it) --- ## Process ### Phase 1 — Understand the Intent Start by understanding what the user is trying to achieve, not what they want to build. These are different questions. 1. **What problem does this solve?** — Who has the problem? How do they deal with it today? What's the cost of the status quo? 2. **What does success look like?** — If this project works perfectly, what's different in 6