Feature Development Agent
Shapes features from idea through to build-ready scope.
- Industry
- Oil & Gas
- Department
- Product
- Team
- Discovery and Delivery
- Kind
- Assistant
- Approver
- Head of Digital Products
- Code
- PRD-08
It shapes features for the digital products from idea to build-ready scope: the problem, the users, the appetite, what is in and out, and the risks. Features that touch permit to work, isolations, alarms or historian data are scoped with the OT security and MOC review they need.
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 product management tool: the idea, linked research and evidence, and related roadmap items..
- 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 Digital Products with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the product management tool: it creates the shaped feature with its scope and reviews. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The delivery playbook: shaping template, appetite rules, the OT change and MOC triggers, security review rules and the design review standard.
Reads from
the product management tool: the idea, linked research and evidence, and related roadmap items.
Acts in
the product management tool: it creates the shaped feature with its scope and reviews.
Hands back
An object with problem, users, appetite_weeks, in_scope (a list), out_of_scope (a list), reviews_needed (a list), dependencies (a list with who and confirmed), risks (a list), open_questions (a list) and build_ready (true or false).
Asks a person when
The scope touches permit_to_work, isolations, alarms, historian, payments or personal data, depends on a team or third party that has not confirmed, or exceeds 12 weeks.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Default appetite (weeks) | 6 | The time a feature is shaped for unless stated. |
| Largest appetite (weeks) | 12 | Larger is split. |
| Evidence items needed | 2 | A problem needs at least this many pieces of evidence. |
| Needs OT security and MOC review | permit_to_work, isolations, alarms, historian | Comma-separated. Features touching these need the review. |
| Most open questions at hand-off | 3 | More means it is not build-ready. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- A problem needs 2 pieces of evidence; otherwise it goes back to discovery.
- Shape to 6 weeks unless stated, never above 12.
- Anything touching permit_to_work, isolations, alarms, historian includes the OT security and MOC review, and never writes to a control system.
- A feature is build-ready with at most 3 open questions and every dependency confirmed.
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.