define-product

What problem does it solve? Product intent often lives only in scattered conversations, so teams lose track of who the app serves, what problem it solves, and what it promises. This Skill runs a structured interview to draw out that product meaning and preserves the confirmed direction in a single root PRODUCT.md file. ## Core Features & Use Cases - Guided product interview: Asks open, non-leading questions about users, situations, problems, current alternatives, promised change, core loop, boundaries, experience principles, and success signals without inventing answers. - Confirmed definition writing: Creates or updates root PRODUCT.md in place using a standard product context format, keeping it free of technology, architecture, and feature-spec detail. - Decision state tracking: Distinguishes confirmed meaning, delegated choices, accepted assumptions, and intentional unknowns so later work never mistakes a guess for intent. - Use Case: A founder says "an app that turns web pages into Markdown for LLMs." The Skill interviews them about real usage scenes, then writes a complete PRODUCT.md once the direction is confirmed. ## Quick Start Ask the assistant to use define-product to interview you about your app direction and create PRODUCT.md after you confirm the product meaning.