New App Feature
OiDetails
Description
Turn a rough product idea into a scoped feature plan with clear user value, UX direction, and implementation shape.
Constraints
Stay scoped to the smallest believable first version. Respect team capacity, technical constraints, and any non-negotiable product boundaries already stated.
Experiments
Surface credible scope cuts, rollout options, and launch variants if they materially improve speed, learning, or adoption.
Measurement
Track whether the feature solves the target problem, is adopted by the intended users, and creates the expected product or business impact.
Definition of done
Done means the team has a clear feature plan with scope, UX direction, implementation shape, launch approach, and an obvious next step to execute.
Post Execution Follow Up
Turn the approved plan into execution-ready tickets, owners, sequencing, and delivery milestones.
Steps
Handoff note
Turn the opportunity into boundaries, tradeoffs, and acceptance criteria.
Handoff note
Describe the interaction model and the rough UX structure needed to ship well.
Handoff note
Propose architecture, sequencing, and the main delivery constraints.
Handoff note
Translate the product and build plan into segment, messaging, channels, and launch readiness.
Guardrails
Require confirmation before continuing with unusually long compiled prompts.
Metadata
Example use cases
Review this feature idea and turn it into a scoped product, design, engineering, and GTM plan.
Take this rough roadmap bet and tell me the smallest credible version we should launch first.
Categories
Tags
Connections