Requirements & User Story Generator

What it does

Turns a raw feature idea — or a "let's add this too" pile — into a requirement package mature enough to enter a sprint without further refinement. The flow has six phases: (Phase 1) it reframes the idea as a JTBD job statement, separating the real "job" from the "feature" that is only a solution hypothesis; (Phase 2) it vertically slices the epic so each story delivers independently observable value — horizontal "backend-first" slicing is rejected, and oversized stories are split with the SPIDR pattern; (Phase 3) each story is scored on the INVEST rubric (0-6) and acceptance criteria are written as Given-When-Then (Gherkin) with at least one happy-path plus one error/alternative scenario per story; (Phase 4) it computes a MoSCoW scope label + RICE score and issues a verdict via a Backlog Readiness Score (0-100).

The output contains the epic & job statement, INVEST-scored story cards, Given-When-Then acceptance criteria, separately tracked NFRs (performance, security, GDPR/KVKK), and a prioritization table. Untestable criteria ("must be fast") are converted to measurable thresholds or moved to gaps.

When to use it

Whenever a feature idea, customer request, or product hypothesis needs to become a structured story set. Ideal user: founder, Business Analyst, Product Owner, or product team. It accepts anything from a one-line request to a multi-feature pile, and measures readiness before backlog refinement so you get a clear "is this sprint-ready" call.

Method / frameworks

• JTBD (Christensen/Ulwick) — need-driven framing around the outcome "hired," not the feature.
• Connextra + 3 C (Jeffries) — Card/Conversation/Confirmation completeness.
• INVEST (Bill Wake) — 0-6 scoring; pass threshold ≥4 plus Testable plus Valuable.
• Gherkin / Given-When-Then (Dan North, BDD) — testable, QA-handoff-ready scenarios.
• MoSCoW + RICE/WSJF — RICE = (Reach × Impact × Confidence) / Effort; WSJF = Cost of Delay / Job Size.
• BABOK v3 (IIBA) — Business/Stakeholder/Solution/Transition layers; NFR separation.
• Definition of Ready — industry-standard readiness gate for the sprint-ready threshold.