Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →product-on-purpose/foundation-build-risk-review
Runs a fast pre-build risk review on a product idea, feature request, or scope change, naming the single assumption most likely to make it fail and returning a clear verdict (build small, validate first, pivot first, or don't build yet) with a no-code validation step. Use before committing build effort, when triaging whether to honor a feature request, or when deciding whether to expand scope, ahead of writing a PRD. For a launched product's pivot-or-persevere decision, use iterate-pivot-decisio
Passed 20 of 22 test cases with the skill, and 5 of 22 without it.
and 18 more in the full report
15 fixed5 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
I have a vague concept for a healthcare productivity app. Give me a risk review on whether to build it.
| Checked | Without skill | With skill |
|---|---|---|
| Asks a single clarifying question completing the sentence framing for who, situation, and problem. | Missed | Passed |
| Limits clarifying inquiries to at most two questions before proceeding. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
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.
| If the ask is | Use instead |
|---|---|
| A launched product's pivot-or-persevere call, weighing usage or market data | iterate-pivot-decision |
| You have chosen the assumption and need to design the test | define-hypothesis |
| Framing a confirmed problem for the team or leadership | define-problem-statement |
| The full nine-block business model, not a single-risk read | foundation-lean-canvas |
| Ranking many features or initiatives against each other | define-prioritization-framework |
The boundary that matters most: this skill is forward-looking and pre-commitment (low or no data); iterate-pivot-decision is retrospective and post-launch (it weighs market feedback on something already shipped).
If the product is already launched and the question is whether to change direction, hand off to iterate-pivot-decision. If the request is too broad to review responsibly, ask exactly one clarifying question (complete the sentence: "this is for [who] in [situation] to solve [problem]"), then proceed. Never run a long questionnaire; at most two questions before a constrained review.
test cases passed, vs 5 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.