{"id":77043,"plugin_id":"plugins_6ab4123730588191bc9267b9458b2670","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:12:20.326Z","digest":"ad3be4af19d350b57d897a60671b94e84d47c4333ef19708f15764c3d2686a1f","against":null,"payload":{"description":"Validate product assumptions and design practical discovery experiments before building.","included_files":[],"name":"validate-idea","skill_md_contents":"---\nname: validate-idea\ndescription: Validate product assumptions and design practical discovery experiments before building.\n---\n\n# Validate Idea\n\n## When to use\nValidate product assumptions and design practical discovery experiments before building.\n\n## Workflow\nFor an idea, list important problem, user, distribution, feasibility and willingness-to-pay assumptions; mark which are user statements versus external research versus hypotheses. Rank assumptions by risk (impact of being wrong, uncertainty, time/cost to test). Choose minimal validation experiments: interview, concierge flow, prototype usability, technical spike or measured test.\n\nDefine expected observation, sample approach, failure condition, stop/continue criteria and caveats. Never fabricate interviews, TAM, conversion, adoption or user satisfaction. If validation is incomplete, say so and recommend what can safely proceed.\n\n## Deliverable and truthfulness\nLead with the decision or result, then show supporting evidence, explicit assumptions, risks, and a concrete next step. Adapt depth to the user's ask. If required tools or source material are missing, disclose the limit; do not simulate inspection, implementation or research. Never write/modify/deploy without relevant authorization.\n\nRelevant reference: `../../references/product-discovery.md`.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}