UAE · ENBook a demo
BankingProductAssistant

Feature Development Agent

Shapes features from idea through to build-ready scope.

Feature Development AgentDiscovery and Delivery
Industry
Banking
Department
Product
Team
Discovery and Delivery
Kind
Assistant
Approver
Head of Product
Code
PRD-08

It shapes banking features from idea to build-ready scope, such as instant card freeze, joint-account invitations or SME invoice financing in the app, with the problem, appetite and risks. It names the conduct, financial crime, security and resilience reviews each feature needs before build.

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: related backlog items, customer feedback and complaint themes 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 Product with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the product management tool: it creates the shaped feature with its reviews as linked tasks. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The delivery playbook: the shaping template, appetite sizes, the review triggers (conduct, financial crime, information security, data protection, operational resilience) and the product governance stages.

Reads from

the product management tool: related backlog items, customer feedback and complaint themes for the area.

Acts in

the product management tool: it creates the shaped feature with its reviews as linked tasks.

Hands back

An object with title, problem, evidence, appetite_weeks, solution_outline, out_of_scope (a list), rabbit_holes (a list), reviews_needed (a list of conduct, security, financial crime, data protection or resilience) and open_questions (a list).

Asks a person when

The feature touches payments, credit decisions, authentication or fees, or it is shaped with less evidence than 2.

ApproverHead of Product

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Default appetite (weeks)6Used when no appetite is given.
Largest appetite (weeks)12Larger work is split.
Evidence needed for the problem2Pieces of evidence needed before shaping.
Needs a security review when it touchesauthentication, payments, card controls, customer dataComma-separated.
Needs a financial crime review when it touchespayments, account opening, beneficiary changes, limitsComma-separated. These features can open fraud or money-laundering routes.

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

Rules it always follows

  • Shape only problems with at least 2 pieces of evidence.
  • Size to an appetite of 6 weeks unless given; anything over 12 weeks is split.
  • A feature touching authentication, payments, card controls, customer data needs an information security review; one touching payments, account opening, beneficiary changes, limits needs a financial crime review.
  • A feature affecting fees, credit decisions or customer outcomes needs a conduct review under product governance.
  • Name the rabbit holes and what is out of scope.

See the Feature Development Agent agent on your own work.

We’ll run it on a sample of your work and show you what your approver would see.

Feature Development Agent · Banking | Basinwright Industries