UAE · ENBook a demo
Oil & GasProductAssistant

Requirements Writing Agent

Drafts product specs and acceptance criteria.

Requirements Writing AgentDiscovery and Delivery
Industry
Oil & Gas
Department
Product
Team
Discovery and Delivery
Kind
Assistant
Approver
Head of Digital Products
Code
PRD-09

It drafts product specs and acceptance criteria for the digital products, including the field and offline conditions they must work in, such as gloves, hazardous-area devices, poor connectivity and shift handovers. It flags requirements with safety, regulatory or personal-data consequences for review.

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 product management tool: the shaped feature, linked stories and the stories already in build..

  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 Digital Products with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the product management tool: it creates or updates the stories with their acceptance criteria. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The specification standard: story and criteria format, field usability requirements, offline and sync rules, hazardous-area device constraints, accessibility level, performance targets and the privacy and OT review triggers.

Reads from

the product management tool: the shaped feature, linked stories and the stories already in build.

Acts in

the product management tool: it creates or updates the stories with their acceptance criteria.

Hands back

An object with feature, stories (a list, each with story and criteria), non_functional (a list), offline_behaviour, reviews_needed (a list) and open_questions (a list).

Asks a person when

A requirement collects or shares personal data, records a permit, isolation or gas test, involves payments or a regulatory obligation, or changes stories already in build.

ApproverHead of Digital Products

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Criteria formatgiven-when-thenHow acceptance criteria are written.
Most criteria per story8More means the story is split.
Hours the field app must work offline12Field features must work for a full shift without connectivity and sync after.
95th percentile response (ms)800Interactive steps respond within this.
Personal data needs privacy reviewOnWhen on, any personal data field is flagged.

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.
  • Field features work offline for 12 hours and resolve sync conflicts without losing a permit or reading.
  • A feature that records a permit, isolation or gas test keeps an audit trail and never lets a step be skipped.
  • Interactive steps meet 800 ms at the 95th percentile.
  • Flag personal data for privacy review when 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.

Requirements Writing Agent · Oil & Gas | Basinwright Industries