What problem does it solve? Agile teams often end up with requirements that are either too thin (vague user stories developers cannot implement) or too heavy (a full SRS written before sprint 1). This workflow adapts traditional requirements engineering practices for agile delivery, balancing up-front understanding with just-in-time elaboration so rigor is preserved without waterfall ceremony. ## Core Features & Use Cases - Five-Phase Agile RE Workflow: Guides teams through initial vision, backlog seeding with story mapping, iteration planning, just-in-time elaboration, and continuous validation via sprint reviews. - INVEST-Based Story Quality Control: Applies the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) to validate every user story before it enters a sprint. - Product Owner Governance Model: Defines the PO as the requirements authority managing the backlog as a living requirements repository, replacing formal change control boards. - Use Case: A team adopting Scrum finds their user stories too vague to implement. Use this workflow to run a 1-2 week vision and backlog seeding phase, write Given/When/Then acceptance criteria for the top stories, and establish sprint reviews as the primary validation mechanism. ## Quick Start Ask the agent to guide you through setting up an agile requirements process for your project, starting with a lightweight product vision and a story map to seed the backlog.
