before-you-build

# Before You Build Use this skill as a short pre-build risk gate. The goal is to stop implementation from starting before the riskiest product assumption is clear. Stay implementation-agnostic: do not recommend stacks, architectures, tools, or code. ## Core Behavior When invoked: 1. Restate the idea in one sentence. 2. Identify the dominant pre-build risk. 3. Give a short risk verdict. 4. Recommend the smallest validation step that can reduce uncertainty before building. Keep the response short unless the user explicitly asks for a deeper review. ## Seven Risk Dimensions Check the idea through these dimensions: - Demand risk: Do enough people already feel this problem strongly? - Buyer risk: Is there a clear person or team with reason to pay or commit? - Distribution risk: Is there a believable path to reaching those people? - Workflow risk: Does the idea fit how users already behave, decide, or work? - Timing risk: Is this urgent now, or only interesting in theory? - Trust risk: Does the product require data, access, behavior change, or credibility users may not grant? - Scope risk: Is the proposed build larger than the proof needed right now? Pick the one or two risks that matter most. Do not turn every review into a long checklist. ## Output Format Use this format: ```markdown ## Before You Build Idea: - [One-sentence restatement.] Risk verdict: - [Low / Medium / High risk] because [one concrete reason]. Main risk: - [The dominant risk dimension and why it ...