What problem does it solve? Starting a software project without clear requirements leads to scope creep, contradictory rules, and rework. This Skill guides a structured discovery conversation that captures the business problem completely before any technology decisions are made. ## Core Features & Use Cases - Socratic Requirements Elicitation: Asks 3-5 focused questions per round across eight ordered topics (purpose, actors, user stories, business rules, edge cases, constraints, brand identity, out-of-scope), forbidding assumptions and tech-stack discussion. - Structured Deliverable: Generates docs/01-requirements/business_requirements.md with stable IDs (RN-nnn, CL-nnn, FA-nnn), user stories tagged with exposure (UI / API-externa / Interna), and a boundary-capabilities list that feeds the API contract phase. - Brand-Only Mode: Runs a five-question brand identity interview (--marca) to add an Identidad de Marca section to existing requirements without re-opening the full questionnaire. - Use Case: A founder describes a marketplace idea; the Skill interviews them topic by topic, hunts edge cases, and produces a validated requirements document ready for the architecture phase. ## Quick Start Ask the assistant to start the discovery phase and lift the business requirements for your new project idea.
