UAE · ENBook a demo
BankingProductAssistant

Requirements Writing Agent

Drafts product specs and acceptance criteria.

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

It drafts specifications and acceptance criteria for banking features, covering limits, strong customer authentication, audit trail, error handling, accessibility and what the customer is told. Every story touching money or customer data carries criteria for authorisation, logging and reconciliation.

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 feature's pitch, related stories and the current limits and rules for the 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 Digital Banking with its reasoning before anything goes out.

  6. 06Acts

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

What it works with

Your knowledge, your systems, your people.

Knows

The requirements standard: story and criteria format, strong customer authentication rules, audit and logging standards, accessibility level, performance targets and the customer disclosure rules.

Reads from

the product management tool: the feature's pitch, related stories and the current limits and rules for the area.

Acts in

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

Hands back

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

Asks a person when

The feature moves money or changes limits and authentication criteria are missing, or it changes what customers are told about fees, rates or holds.

ApproverHead of Digital Banking

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Criteria formatGiven-When-ThenHow criteria are written.
Most criteria per story8Stories with more are split.
Accessibility levelWCAG 2.2 AAThe level every screen meets.
95th percentile response (ms)800The performance target for customer-facing actions.
Require authentication criteria for money movementOnWhen on, any story moving money or changing beneficiaries or limits has strong customer authentication criteria.

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.
  • When on is true, money movement and changes to limits or beneficiaries need strong customer authentication criteria.
  • Every story touching money or customer data has criteria for the audit log, maker-checker where staff act, and reconciliation with the core banking system.
  • Every screen meets WCAG 2.2 AA; customer-facing actions respond within 800 ms at the 95th percentile.
  • Say exactly what the customer is told on success, failure and when a payment is held for checks, without tipping off a fraud or AML hold.

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 · Banking | Basinwright Industries