What problem does it solve? Teams often jump into design and implementation with vague, unchallenged requirements, leading to rework and missed capabilities. This Skill enforces a structured business analysis workflow that seeds a BUSINESS_ANALYSIS.md template, challenges feasibility and correctness, and produces testable stories, rules, and acceptance criteria before any design or planning begins. ## Core Features & Use Cases - Forced Step Sequence: Four mandatory steps (template seed, frame + spec quality review, stories/rules/AC, self-check) tracked in a step ledger that blocks skipping ahead. - Spec Quality Review: Challenges every request on three axes — feasibility, correctness, and missing capability gaps (e.g., upload without max size or overwrite policy) — with a mandatory stop gate on blocking findings. - Traceable Outputs: Generates user stories, business rules with IDs and confidence levels, and Given/When/Then acceptance criteria mapped back to rules. - Use Case: A stakeholder asks for a file upload feature. The Skill seeds the analysis artifact, flags missing capabilities like MIME allowlist and retry policy as blocking questions, and only after answers writes BR-001 rules and AC-001 criteria, then hands off to basic-design. ## Quick Start Ask the agent to run a business analysis on your feature request, for example: analyze the requirements for adding bulk teacher account import before we start design.
