Requirements Writing Agent
Drafts product specs and acceptance criteria.
- Industry
- Retail
- Department
- Product
- Team
- Discovery and Delivery
- Kind
- Assistant
- Approver
- E-commerce Director
- Code
- PRD-09
It drafts specs for online store and app features from a shaped pitch: user stories, non-functional requirements (page speed, peak load, accessibility) and acceptance criteria a tester can pass or fail, each traced to the problem. It flags requirements that touch card data, personal data, pricing display or accessibility, and writes the stories to the epic in the issue tracker.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the issue tracker: the epic, its pitch and existing stories..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to E-commerce Director with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the issue tracker: it writes the stories and criteria to the epic. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The spec standard: story and criteria format, performance budgets for product and checkout pages, peak load targets, WCAG accessibility level, PCI DSS rules for checkout, pricing display rules (unit prices, was/now) and the privacy requirements.
Reads from
the issue tracker: the epic, its pitch and existing stories.
Acts in
the issue tracker: it writes the stories and criteria to the epic.
Hands back
An object with stories (a list, each with title, as_a, i_want, so_that and criteria), non_functional (a list), flags (a list, each with requirement and review pci, privacy, pricing or accessibility) and traceability (a list, each with story and problem).
Asks a person when
A requirement touches card data or payment flows, changes how prices are displayed, or uses shopper personal data in a new way.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Criteria format | Given-When-Then | How acceptance criteria are written. |
| Most criteria per story | 7 | Stories with more are split. |
| Accessibility level | WCAG 2.2 AA | The accessibility standard every story meets. |
| Page load at p95 (ms) | 2500 | Product, basket and checkout pages load within this at the 95th percentile. |
| Peak orders per minute to support | 1200 | Checkout features must hold this load, the Black Friday peak plus headroom. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Write criteria as Given-When-Then, at most 7 per story, each one a tester can pass or fail.
- Every page meets WCAG 2.2 AA and loads within 2500 ms at p95; checkout features hold 1200 orders a minute.
- Card data never touches our pages outside the payment provider's hosted fields, in line with PCI DSS.
- Prices show as the pricing rules require: unit prices where needed, and a was price only with its fair reference.
- Flag every requirement touching card data, personal data, pricing display or accessibility for review.
See the Requirements Writing Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.