problem-analysis

Convert solution-oriented requests into structured problem analysis with impact mapping and JTBD.

Updated May 10, 2026
One-click install
npx skills add https://github.com/rob-broadley/ai-airbase --skill problem-analysis-rob-broadley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-analysis
Source: https://github.com/rob-broadley/ai-airbase/tree/main/cadre/skills/problem-analysis
Command: npx skills add https://github.com/rob-broadley/ai-airbase --skill problem-analysis-rob-broadley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents teams from building the wrong thing by turning vague requests into a clear, testable understanding of goals, actors, impacts, constraints, risks, and confidence.

Core Features & Use Cases

  • Impact Mapping to connect every deliverable back to the goal it serves, ensuring decisions trace to business outcomes rather than features.
  • Jobs To Be Done (JTBD) to reframe solution-first requests into the underlying user job, avoiding duplicated or misdirected effort.
  • Contradiction, NFRs, Constraints, and Premortem to surface hidden tensions, missing requirements, practical boundaries, and plausible failure modes before story writing or planning.

Use cases include: turning a feature idea into requirements that explain why it matters, decomposing a product initiative while detecting trade-offs and unknowns, and running a structured premortem to de-risk delivery.

Quick Start

Ask an AI assistant to perform problem analysis for your initiative by running Impact Mapping, deriving JTBD statements, identifying contradictions and constraints, enumerating non-functional requirements as open questions, conducting a premortem, and producing confidence scores across stakeholders, context, outcomes, constraints, and risks.

Frequently Asked Questions about problem-analysis

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

FAQPage Schema
How do I turn a vague feature request into structured requirements analysis?

To turn a vague feature request into structured requirements analysis, you reframe solution-oriented requests by defining goals, actors, impacts, and underlying user jobs. This ensures your deliverables trace directly to business outcomes rather than arbitrary features.

What is the best way to run a premortem for product risk assessment?

Running a premortem for product risk assessment involves identifying plausible failure modes before story writing or planning begins. You classify contradictions and constraints by taxonomy to surface hidden tensions and practical boundaries early in the process.

How does impact mapping validate deliverables during problem analysis?

Impact mapping validates deliverables by connecting every output back to the specific goal it serves. This ensures decisions trace to business outcomes and prevents teams from building features that lack clear strategic alignment.

How do I identify non-functional requirements as open questions during feature decomposition?

Identifying non-functional requirements as open questions involves enumerating practical constraints and gaps that surface during feature decomposition. This process highlights missing requirements and hidden tensions before they impact delivery.

When should confidence scoring block handoff in problem analysis?

Confidence scoring blocks handoff in problem analysis when any dimension—stakeholders, context, outcomes, constraints, or risks—scores below 6. This threshold prevents teams from proceeding to planning with insufficient understanding.