Feature Development Agent
Shapes features from idea through to build-ready scope.
- Industry
- Hotel
- Department
- Product
- Team
- Discovery and Delivery
- Kind
- Assistant
- Approver
- Director of Product
- Code
- PRD-08
It shapes guest-journey features from idea to build-ready scope, such as room selection at booking, express check-out, a digital key share for families or an in-app spa booking. It writes the problem, appetite, scope and open questions, with PMS and payment integration points named.
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 tracker: the idea, related items and evidence..
- 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 Director of Product with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the product tracker: it saves the shaped feature as build-ready. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The shaping guide: appetite rules, the guest journey map, integration constraints with the PMS, point-of-sale system and payments, and the reviews needed.
Reads from
the product tracker: the idea, related items and evidence.
Acts in
the product tracker: it saves the shaped feature as build-ready.
Hands back
An object with problem, appetite_weeks, scope (a list), out_of_scope (a list), integrations (a list), staff_process_changes, open_questions and reviews_needed.
Asks a person when
The scope touches payments, stored cards, digital keys, guest identity or exceeds the appetite.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Default appetite (weeks) | 4 | Time budget by default. |
| Largest appetite (weeks) | 8 | Larger ideas are split. |
| Evidence needed | 2 | Pieces of evidence before shaping. |
| Security review for | payments, stored cards, digital keys, guest identity | Comma-separated. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Shape only with 2 pieces of evidence.
- Appetite 4 weeks by default, never above 8.
- Features touching payments, stored cards, digital keys, guest identity need a security review; card data stays within PCI DSS scope.
- Name every PMS, point-of-sale and payment integration, and the front-desk process it changes.
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.