four-risks

Assess feature proposals against value, usability, feasibility, and viability risks.

16|3|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/breethomas/bette-think --skill four-risks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: four-risks
Source: https://github.com/breethomas/bette-think/tree/main/plugins/bette-think/skills/four-risks
Command: npx skills add https://github.com/breethomas/bette-think --skill four-risks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams waste time and resources building features that fail because core risks were not evaluated early; this Skill provides a fast, structured assessment to surface value, usability, feasibility, and viability risks before development begins.

Core Features & Use Cases

  • Four-dimension risk assessment: Produces High/Medium/Low ratings for Value, Usability, Feasibility, and Viability with concise rationale for each.
  • Actionable de-risking guidance: Lists key questions, recommended discovery activities, and a short plan to reduce top risks.
  • Integrations & modes: Works from Linear or GitHub issue text when MCPs are configured or accepts a manual feature description for ad-hoc reviews.
  • Use case example: Run this on a proposed AI email composer feature to determine whether customer demand, usability, engineering feasibility, and business economics are sufficient to proceed.

Quick Start

Run a Four Risks assessment on issue ENG-245 and return per-risk ratings, key de-risk questions, and a recommended next-step discovery plan.

Frequently Asked Questions about four-risks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I assess product risks for a feature proposal before development?

Assess feature proposals by evaluating value, usability, feasibility, and viability risks to produce per-risk ratings, de-risking questions, and recommended discovery activities before engineering begins.

Can I run a risk assessment directly on Linear or GitHub issues?

Yes, you can run risk assessments directly on Linear or GitHub issue text when MCPs are configured, or manually paste a feature description to evaluate product risks ad-hoc.

What are the four critical risks to evaluate during product discovery?

The four critical product risks are value, usability, feasibility, and viability, which together determine whether customer demand, user experience, engineering scope, and business economics support proceeding with a feature.

How do I get actionable de-risking guidance after evaluating a feature?

After evaluating a feature, the assessment outputs High/Medium/Low per-risk ratings with concise rationale, key de-risking questions, and a short plan of recommended discovery activities to reduce top risks.

Does the four risks evaluation work for an entire sprint backlog or just individual issues?

The risk evaluation works for individual issue pages, current sprint issue lists, or manual feature descriptions, allowing you to validate single ideas or review an entire sprint backlog before building.

Can I add risk assessment comments back to the original Linear or GitHub issue?

Yes, the assessment can optionally add comments containing the per-risk ratings, de-risking questions, and recommended discovery plan directly to the source Linear or GitHub issue.