dsh-product

Many products get stuck in an uncomfortable gap: the opportunity has been validated, the direction is right, yet there is no clear gate from product definition, POC, MVP, to PMF review. Sales or beta feedback often ends at "a doc was written, so we are done," and never drives a concrete next action. dsh-product exists to fill that gap, turning a confirmed product opportunity into something verifiable, shippable, and iterable.

Three pillars define its core capability. First, it combines public web research with local Markdown, CSV, JSON, and JSONL evidence to give product definitions and scope boundaries a traceable, factual foundation. Second, built-in checks — product_artifact_review for handoff artifacts and product_feedback_close for binding sales or beta feedback to an action, owner, due date, and explicit verification state — eliminate the false sense of closure that documentation alone provides. Third, PMF evidence serves as the decision criterion for proceed, adjust, or pause, and once a proceed or scale decision is made, a versioned handoff contract carries value evidence and delivery boundaries to downstream plugins such as dsh-sales, dsh-growth, and dsh-geo.

It is designed for individual developers, small product teams, and anyone owning the product-definition and delivery stage within the dsh six-plugin workflow. It writes no code, touches no design files, and creates no CRM records. Its focus is singular: making "what to build, how small to start, and how to measure" explicit and evidence-backed, so every product decision stands on solid ground.