Agent skill · Code Review & Quality

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-decision instead.

product-on-purposegithub.com/product-on-purposeGitHub ↗
claude-codecodexApache-2.0
Install
npx skills add product-on-purpose/pm-skills --skill foundation-build-risk-review --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 8
SKILL.md size: 7 KB
Bundled scripts: none
Version: 1.0.1
Declared author: product-on-purpose
Path: skills/foundation-build-risk-review/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 518
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> <!-- Adapted from bin1874/before-you-build-skill (Apache-2.0), repositioned PM-neutral. --> # 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 cha

What's inside
Steps it walks through
  1. Hard gate
  2. When to Use
  3. When NOT to Use
  4. Modes (route first; state the mode at the top)
  5. The review (the contract)
  6. Verdict routing
  7. Output Format
  8. Quality Checklist
  9. Attribution
Ships with 7 files
  • HISTORY.md
  • evals/output-scenarios/ai-meeting-summarizer.md
  • evals/trigger-fixtures.json
  • references/EXAMPLE.md
  • references/TEMPLATE.md
  • references/risk-taxonomy.md
  • references/routing-map.md
More from pm-skills
All skills →
About this skill
What does the foundation-build-risk-review skill do?

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-decision instead.

How do I install it?

Run `npx skills add product-on-purpose/pm-skills --skill foundation-build-risk-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From product-on-purpose/pm-skills, a repository with 518 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going