The mandate
Turn customer evidence into the smallest release that can teach the company something.
Converts evidence into product strategy, requirements, milestones, acceptance criteria, and learning loops.
The Product Agent translates observed needs into outcomes, non-goals, requirements, release slices, and acceptance criteria. It prevents a requested feature from becoming a roadmap commitment before the underlying assumption is understood.
What to bring
Bring one workflow, one target user, and the evidence behind the problem.
The brief should include current behavior and constraints as well as the desired outcome. A feature list without customer evidence is not enough.
- 01
The product area, customer journey, or workflow being planned.
- 02
The user, situation, current alternative, and desired outcome.
- 03
Observed behavior, interviews, support evidence, usage data, and unresolved assumptions.
- 04
Time, platform, legal, technical, design, commercial, and dependency constraints.
- 05
The customer outcome and material assumption the next release must test.
What you receive
A strategy and release plan that remain testable.
Product strategy, prioritized requirements, and release slices share the same customer outcome, evidence, dependencies, and learning objective.
- 01
Product strategy
product/strategy.mdReady when
Customer, problem, outcome, constraints, and non-goals are explicit.
- 02
Prioritized requirements
product/requirements.jsonReady when
Each requirement has evidence and acceptance criteria.
- 03
Incremental release plan
product/releases.mdReady when
Every slice is independently testable by a target customer.
The method
Frame the outcome, slice the risk, and decide what the release must prove.
The Product Agent deliberately narrows scope until the next release can be used, measured, and discussed with a target customer.
- 1
Frame
Define the user, current behavior, desired outcome, evidence, constraints, and non-goals.
- 2
Slice
Choose the smallest independently useful release that tests a material assumption.
- 3
Specify
Write requirements, dependencies, edge cases, and observable acceptance criteria.
- 4
Learn
Plan customer validation, evidence capture, and the decision that follows the release.
Signals & guardrails
Scope is not validated merely because it fits on a roadmap.
Requirements without evidence, hidden dependencies, and release slices that cannot independently test an outcome remain unresolved product risks.
Signs the work is useful
- Primary workflow completion
- Time to first value
- Validated learning per release
Reasons to pause
- Feature scope is not linked to evidence
- Roadmap commitments hide unresolved dependencies
Approval boundary
This entrypoint declares no open-world effect. Applying its todos still requires an authenticated, scoped project run.
Technical appendix
The exact contract behind the profile.
Useful for operators who need to inspect the immutable Kit version, typed boundary, and verification surface.
- Kit
- company-suite@0.1.0
- Entrypoint
- plan-product
- Function
- plan-product
- Runtime
- python@3.12
- Input
- specialist-brief.schema.json
- Output
- specialist-plan.schema.json
Verification
specialist-plan-quality · specialist-plan-schema
Connected systems
No external connector required