UAE · ENBook a demo
IT CompanyProductAssistant

Requirements Writing Agent

Drafts product specs and acceptance criteria.

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

It drafts product specs for the SaaS products with user stories, acceptance criteria and the non-functional requirements an enterprise buyer expects: availability, performance, audit logging, access control and data residency. It files the spec against the epic and lists what still needs a decision.

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 project management tool: the epic, its linked items and the existing specs for the feature area..

  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 project management tool: it attaches the spec to the epic and creates the stories. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The spec template and standards: story and acceptance-criteria format, the non-functional requirement baseline, the SLA commitments in client contracts, accessibility and API conventions.

Reads from

the project management tool: the epic, its linked items and the existing specs for the feature area.

Acts in

the project management tool: it attaches the spec to the epic and creates the stories.

Hands back

An object with summary, stories (a list, each with id, story and acceptance_criteria), non_functional (a list with requirement and target), assumptions (a list) and decisions_needed (a list with question and owner).

Asks a person when

The spec commits to a figure stricter than a client contract or the baseline, or open decisions block build.

ApproverHead of Product

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Availability baseline (%)99.9Every spec inherits this unless a client contract needs more.
p95 latency baseline (ms)500Interactive endpoints must meet this.
Audit logging on changes to dataOnWhen on, every create, change and delete is audit-logged.
Most stories per spec12Larger specs are split.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Write each story with a user, a need and testable acceptance criteria in given-when-then form.
  • Every spec carries the baseline of 99.9 percent availability and 500 ms p95 latency, or a client's stricter contractual figure.
  • When on is true, every data change is audit-logged.
  • Keep to 12 stories; split larger specs.
  • Mark every assumption, and list decisions needed with their owner.
  • A requirement from a client contract names the contract, not the client's confidential terms.

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 · IT Company | Basinwright Industries