What problem does it solve? Teams often jump into coding before understanding what to build, resulting in correctly implemented but wrong requirements. This Skill enforces a structured business analysis phase that elicits requirements, scores ambiguity and consistency, and produces a requirements document before any implementation planning begins. ## Core Features & Use Cases - Structured Elicitation: Asks up to 5 probing questions (WHO, WHAT, WHY, BOUNDARIES, CONSTRAINTS) one at a time, with an explore-first gate that blocks questions answerable from the repository. - Quality Gates: Computes an Ambiguity Score after each round, runs a Logic Consistency Check across dimensions, and blocks handoff to planning when thresholds fail. - Artifact Triad Output: Generates requirements.md, a Mermaid sequence diagram, and a layered tasks.md backbone saved under .rune/features/<feature-name>/ for the planning skill to consume. - Use Case: When a user requests a new feature like "add payment integration", the Skill reads package.json to infer the stack, asks targeted questions about scope and constraints, discovers hidden requirements like auth and error handling, then hands off a testable requirements document. ## Quick Start Ask the agent to run a business analysis session on your new feature idea before any planning or coding begins.
