What problem does it solve? Turning a vague software project idea into validated, documented requirements is error-prone: requirements get fabricated, NFRs stay vague, and ownership of feasibility or sign-off gets blurred. This Skill walks an AI agent through a structured six-stage business-analysis workflow so every requirement is testable, traceable, and owned by the right human role. ## Core Features & Use Cases - Six-stage workflow: define problem and goals, analyze the as-is state, gather functional and non-functional requirements, design the to-be state, assess feasibility, then validate and document. - Mode detection: detects whether the agent acts as an autonomous BA or as a co-pilot to a human BA, and adjusts ownership behavior accordingly. - Anti-fabrication rules: technical feasibility, effort estimates, and test results are never invented; they are routed to named human owners via labeled placeholders. - Ready-made artifacts: templates for BRD/SRS documents, user stories with acceptance criteria, a requirements checklist, and a RACI matrix, plus reference guides for elicitation questions, NFR targets, and requirements techniques. - Use Case: Ask the agent to run the analysis for adding saved payment cards to checkout; it produces a BRD/SRS with measurable goals, user stories with Given/When/Then acceptance criteria, numeric NFRs, and flags feasibility verdicts for the tech lead. ## Quick Start Ask the agent to run a business analysis for your feature, for example: "You're the BA — run the analysis for adding saved payment cards to checkout."
