Feature Development Agent
Shapes features from idea through to build-ready scope.
- Industry
- Procure AI
- Department
- Product
- Team
- Discovery and Delivery
- Kind
- Assistant
- Approver
- Head of Product
- Code
- PRD-08
It shapes a platform feature from idea to build-ready scope, such as split-delivery goods receipts, supplier self-service bank-detail changes or a reverse-auction extension rule: the problem and evidence, who it is for, the appetite, the solution outline, what is out of scope and the dependencies. It flags any scope that touches payments, supplier bank details, approval limits or segregation of duties and creates the epic with first-cut stories in the issue tracker.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the issue tracker: related epics, client tickets and the dependency owners..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Head of Product with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the issue tracker: it creates the epic with its first-cut stories. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The shaping method, the platform architecture and integrations with client ERPs, the controls that features must not weaken (segregation of duties, delegation of authority, bank-change verification) and past shaped features.
Reads from
the issue tracker: related epics, client tickets and the dependency owners.
Acts in
the issue tracker: it creates the epic with its first-cut stories.
Hands back
An object with title, problem, evidence, users, appetite_weeks, solution_outline, out_of_scope, rabbit_holes, dependencies (a list with dependency and confirmed), controls_review_needed, readiness (ready, needs_review or not_ready) and stories.
Asks a person when
The scope touches payments, supplier bank details, approval limits or segregation of duties, depends on a team or client system that has not confirmed, or exceeded 12 weeks before it was split.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Default appetite (weeks) | 6 | The time box when none is given. |
| Largest appetite before splitting (weeks) | 12 | Larger scopes are split. |
| Evidence needed for the problem | 2 | Independent pieces of evidence needed. |
| Scope that needs a controls review | payments, supplier bank details, approval limits, segregation of duties | Scope that touches these needs a controls review. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- A feature is shaped only with at least 2 pieces of evidence for the problem.
- Scope fits the appetite, 6 weeks by default; above 12 weeks it is split.
- Scope touching payments, supplier bank details, approval limits, segregation of duties gets a controls review before it is build-ready.
- A dependency on a client ERP integration or a third party is unconfirmed until its owner agrees a date.
- Out of scope and rabbit holes are written down, never left implied.
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.