Build Risk Review

Don't build it yet. First name the one assumption most likely to make it fail.

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.

Hard gate

Do 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.

If 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.

When to use

• A product idea, MVP, or new bet is about to turn into build work.
• A feature request or scope change has arrived and you need to separate real demand from a polite ask, founder anxiety, or competitor-copying.
• Someone wants a fast "should we build this?" verdict before a PRD, roadmap row, or ticket exists.