UAE · ENBook a demo
Procure AIProductAssistant

Requirements Writing Agent

Drafts product specs and acceptance criteria.

Requirements Writing AgentDiscovery and Delivery
Industry
Procure AI
Department
Product
Team
Discovery and Delivery
Kind
Assistant
Approver
Head of Product
Code
PRD-09

It drafts specs for platform features: user stories, non-functional requirements and acceptance criteria a tester can pass or fail, each traced to the problem. It flags requirements that touch supplier or client personal data, payment files, e-invoicing tax fields or audit trails, and writes the stories to the epic in the issue tracker.

How it works

6 steps, and a person signs off before step 6.

  1. 01Looks it up

    Finds the record the request is about in the issue tracker: the epic, its shaped scope and the stories already in progress..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Works it through

    Prepares the draft, match, recommendation or reply, with its sources.

  5. 05Asks a person

    Hands the work to Head of Product with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the issue tracker: it writes the stories and acceptance criteria to the epic. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The spec template, acceptance criteria style, non-functional standards (latency, availability, audit logging), country e-invoicing and tax field rules, and the data protection requirements for supplier and client data.

Reads from

the issue tracker: the epic, its shaped scope and the stories already in progress.

Acts in

the issue tracker: it writes the stories and acceptance criteria to the epic.

Hands back

An object with feature, stories (a list with story, role, criteria and trace_to_problem), non_functional (a list), compliance_flags (a list with requirement and reason) and open_questions.

Asks a person when

A requirement handles personal data or bank details, a payment file or a tax or e-invoicing obligation, or the spec changes stories already in progress.

ApproverHead of Product

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Acceptance criteria formatGiven-When-ThenHow criteria are written.
Criteria per story7Stories with more are split.
Response time at p95 (ms)800The default response time requirement.
Require an audit trail on approvals and changesOnWhen on, every approval, change of amount or supplier field is logged with who and when.
Privacy review for personal dataOnWhen on, requirements touching personal data are flagged for 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 7 per story, each pass or fail.
  • Every approval, amount change and supplier master change is logged when on is true.
  • A requirement for an e-invoicing or tax field names the country rule it follows.
  • When on is true, any requirement on supplier contacts, bank details or requisitioner data is flagged.
  • Interactive screens meet 800 ms at p95 unless the spec says otherwise.

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.

Requirements Writing Agent · Procure AI | Basinwright Industries