agentic-product-discoverylisted

# Agentic Product Discovery Turn uncertainty into explicit decisions. End with a ratified contract another agent can use without reconstructing the discovery conversation. Worked examples and provenance: `examples.md`. > Explore broadly enough to expose meaningful choices, then narrow deliberately > until product behavior and visual direction are durable artifacts rather than > memories in a chat. --- ## 1. Own the product question, not every downstream technique Own: - problem, audience, desired outcome, and current workflow; - build-vs-buy and scope/value tradeoffs; - product boundaries, requirements, workflows, and information architecture; - experience principles and interaction direction; - iterative visual and brand refinement; - explicit decision states and deferred ideas; and - the ratified handoff into specification and architecture. Do not own implementation architecture, production UI code, or delivery. Use the routing table in §7 as soon as another skill becomes the better specialist. Discovery may produce wireframes, comparison panels, or prototypes as evidence, but those artifacts answer a product or design question; they are not permission to begin the build. --- ## 2. Choose the smallest useful discovery lane | Lane | Use for | Expected shape | |---|---|---| | **Quick** | One bounded feature or a mostly settled direction | 1–2 question rounds, 2–3 options, short decision record | | **Standard** | A new product or meaningful capability | Problem/work