Requirements Writing Agent
Drafts product specs and acceptance criteria.
- Industry
- Hotel
- Department
- Product
- Team
- Discovery and Delivery
- Kind
- Assistant
- Approver
- Director of Product
- Code
- PRD-09
It drafts specs and acceptance criteria for guest-facing features, such as the booking engine's payment step, digital registration cards or a loyalty points display. It writes testable criteria including tax display, card handling and accessibility.
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 product tracker: the feature and related specs..
- 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 Director of Product with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the product tracker: it saves the spec on the feature. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The spec template: story format, acceptance criteria rules, accessibility level, tax and fee display rules by market, and card data rules.
Reads from
the product tracker: the feature and related specs.
Acts in
the product tracker: it saves the spec on the feature.
Hands back
An object with stories (a list, each with story and criteria), non_functional, data_collected and reviews_needed.
Asks a person when
The spec collects new guest data or changes card handling.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Criteria format | given-when-then | How criteria are written. |
| Most criteria per story | 8 | Larger stories are split. |
| Accessibility level | WCAG 2.2 AA | The level to meet. |
| Privacy review for guest data | On | When on, specs collecting guest data get a privacy review. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Write criteria as given-when-then, at most 8 per story.
- Meet WCAG 2.2 AA.
- Prices show taxes and fees as each market requires; card numbers are never stored outside the payment provider's vault.
- Specs collecting guest data get a privacy review while on is true.
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.