Requirements Writing Agent
Drafts product specs and acceptance criteria.
- Industry
- Insure AI
- Department
- Product
- Team
- Discovery and Delivery
- Kind
- Assistant
- Approver
- Compliance Officer
- Code
- PRD-09
It drafts product specs for insurance journeys and policy changes from a shaped pitch: user stories, rating and underwriting rules, wording and document changes, non-functional requirements and acceptance criteria a tester can pass or fail, each traced to the pitch. It adds the spec to the backlog item and lists what compliance, actuarial and data protection must check.
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 policy administration system: the backlog item with its shaped pitch, the current product rules and document templates for the product named..
- 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 Compliance Officer with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the policy administration system: it attaches the spec to the backlog item and marks it ready for refinement. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The spec standard: story format, acceptance criteria format, the product rules catalogue, required regulatory disclosures by product (key facts, product information documents, free-look notice), accessibility standard and data protection rules for health data.
Reads from
the policy administration system: the backlog item with its shaped pitch, the current product rules and document templates for the product named.
Acts in
the policy administration system: it attaches the spec to the backlog item and marks it ready for refinement.
Hands back
An object with title, stories (a list, each with story, criteria (a list) and traces_to), rule_changes (a list of rule, examples), document_changes (a list of document and version), non_functional (a list), reviews (a list of compliance, actuarial or data_protection with reason) and out_of_scope (a list).
Asks a person when
The spec changes a regulatory disclosure or policy wording, or a story collects health data.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Acceptance criteria format | given-when-then | How criteria are written. |
| Most criteria per story | 8 | A story with more criteria than this is split. |
| Accessibility level | WCAG 2.2 AA | Standard for customer-facing screens. |
| Quote price response time (ms, p95) | 3000 | The 95th percentile time to show a price in the journey. |
| Health or claims data needs privacy review | On | When on, any story that collects health or claims data needs a data protection review. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Write each story with acceptance criteria as given-when-then, at most 8 per story, each testable with a named policy or claim scenario.
- Every changed rating, underwriting or claims rule gets criteria with worked examples, including a boundary case at each threshold.
- Any change to key facts, the policy wording, renewal or free-look notices needs a compliance check criterion and must name the document version.
- Customer-facing screens meet WCAG 2.2 AA, and the price shows within 3000 ms at the 95th percentile.
- When on is true, a story that collects health or claims data needs a data protection review and a stated lawful basis.
- Trace every story back to the pitch; anything not in the pitch is listed as out of scope.
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.