value-and-viable

Clarify root cause and user need before implementation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mykaarma/claude-sutras --skill value-and-viable
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: value-and-viable
Source: https://github.com/mykaarma/claude-sutras/tree/main/skills/value-and-viable
Command: npx skills add https://github.com/mykaarma/claude-sutras --skill value-and-viable

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that teams identify the true root cause and articulate user outcomes before starting any implementation work, preventing scope drift and misaligned effort.

Core Features & Use Cases

  • Problem framing: Guides teams to articulate observed issues, stakeholders, triggers, and impact.
  • Root-cause analysis: Encourages structured methods (e.g., 5 Whys) to uncover fundamental needs.
  • User need alignment: Captures outcomes in JTBD style to drive value-driven work.
  • Solution exploration and viability: Prompts multiple approaches with trade-offs and a clear selection rationale.
  • Measurement and governance: Establishes success metrics, kill criteria, and review cadence to govern ongoing work.

Quick Start

Begin by documenting the problem and identifying the root cause, then clearly state the user outcome before proposing any solution.

Frequently Asked Questions about value-and-viable

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

FAQPage Schema
How do I validate the right problem before building a solution?▼

To validate the right problem before building, articulate the observed issue, identify stakeholders, and conduct root-cause analysis using methods like the 5 Whys before proposing any implementation.

What is root-cause analysis and how does it align with user needs?▼

Root-cause analysis uncovers fundamental needs through structured methods like the 5 Whys, while user need alignment captures these outcomes in JTBD style to drive value-driven work.

How do I define kill criteria and success metrics for a new project?▼

Define kill criteria and success metrics by establishing measurable outcomes, setting a review cadence, and documenting clear governance parameters to evaluate ongoing viability.

Can I explore multiple solution approaches with trade-offs before implementation?▼

Yes, solution exploration prompts multiple approaches with clear trade-offs and a selection rationale to ensure the chosen path is viable and addresses the validated root cause.

When do I need a structured problem statement for product management?▼

You need a structured problem statement when you observe scope drift or misaligned effort, ensuring teams frame the issue, identify triggers, and articulate user outcomes before implementation.