Feature Development Agent
Shapes features from idea through to build-ready scope.
- Industry
- IT Company
- Department
- Product
- Team
- Discovery and Delivery
- Kind
- Assistant
- Approver
- Head of Product
- Code
- PRD-08
It shapes a feature from idea to build-ready scope for the SaaS products: problem, users, options, the smallest valuable version, effort range, and the security, data-protection and multi-tenancy questions to answer before build. It files the shaped pitch on the backlog and flags anything that needs a security or architecture review.
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 project management tool: the backlog item, linked client requests, related features and past decisions..
- 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 project management tool: it updates the backlog item with the shaped pitch and its status. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The shaping guide: the pitch template, appetite sizes, the architecture principles, multi-tenancy and data-residency rules, and the security review triggers.
Reads from
the project management tool: the backlog item, linked client requests, related features and past decisions.
Acts in
the project management tool: it updates the backlog item with the shaped pitch and its status.
Hands back
An object with problem, users, options (a list with option, effort_weeks and trade_off), chosen_scope, out_of_scope, reviews_needed (a list), open_questions (a list) and build_ready (true or false).
Asks a person when
The feature is client-specific, needs a security or architecture review, or exceeds 6 engineer-weeks.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Default appetite (engineer-weeks) | 6 | The size the smallest version must fit when none is given. |
| Security review when personal data is touched | On | When on, a feature handling new personal or client data needs a security review. |
| Most open questions before build | 3 | A pitch with more is not build-ready. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Fit the smallest valuable version within 6 engineer-weeks unless the request sets an appetite.
- When on is true, a feature touching new personal or client data needs a security review.
- Every feature states how it works for multi-tenant isolation and data residency.
- A pitch with more than 3 open questions is not build-ready.
- A feature for one client is flagged client-specific and goes to the Head of Product.
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.