StoryForge · Requirements to Backlog

StoryForge Requirements-to-backlog workflow

connecting

Source & evals API

1Source notes

Try an example:

0 words0 / 40,000 characters

2Model backend

Live models Offline stub

Gemini 2.5 Flash with Groq as fallback. Real model output; a few minutes per run.

Prompt version

Review rounds

0 1 2

Failing stories go back to the writer up to 2 times.

—

Five agents, deterministic guardrails after every call. Ctrl Enter runs.

3Agent pipeline

1
Intake
Goals, stakeholders, constraints, out-of-scope
2
Requirements
Atomic statements with verbatim evidence; traceability guardrail
3
Stories
Epics, user stories, Given / When / Then
4
INVEST review
Scores, pass / fail; failing stories sent back to the writer
5
Gap analysis
Uncovered goals, missing NFRs, questions to ask