foundation-build-risk-review

1<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
2<!-- Adapted from bin1874/before-you-build-skill (Apache-2.0), repositioned PM-neutral. -->
3# Build Risk Review
4 
5Don't build it yet. First name the one assumption most likely to make it fail.
6 
7`foundation-build-risk-review` is a fast, pre-commitment gate for product decisions. Given an idea, a feature request, or a scope change, it returns a **Build Risk Review**: the single biggest risk, the evidence behind it, a verdict, and a concrete no-code validation step, then routes you to the skill that does the next piece of work. It is a foundation hub: its job is to triage and dispatch, not to duplicate the deeper skills.
8 
9## Hard gate
10 
11Do not write code, scaffold a project, recommend a stack, or design implementation. First answer three things: should this be built, what is most likely to make it fail, and what must be validated before committing.
12 
13If the user says the work is for learning, a portfolio, or internal practice, do not judge it by market standards; still flag scope and clarity risks.
14 
15## When to Use
16 
17- A product idea, MVP, or new bet is about to turn into build work.
18- A feature request or scope change has arrived and you need to separate real demand from a polite ask, founder anxiety, or competitor-copying.
19- Someone wants a fast "should we build this?" verdict before a PRD, roadmap row, or ticket exists.
20 
21## When NOT to Use
22 
23| If the ask is | Use instead |
24|---|---|
25…