problem-framing

Convert an approved intake route into a problem statement and design directions.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/yknothing/prodcraft --skill problem-framing-yknothing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-framing
Source: https://github.com/yknothing/prodcraft/tree/main/skills/00-discovery/problem-framing
Command: npx skills add https://github.com/yknothing/prodcraft --skill problem-framing-yknothing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts an approved intake route into a crisp, decision-ready problem statement that guides downstream discovery and design work.

Core Features & Use Cases

  • Produces a structured problem-frame including problem statement, target users, constraints, non-goals, assumptions, and open questions
  • Generates 2-3 viable directions in an options-brief with trade-offs and recommended next steps
  • Recommends a design-direction and the next lifecycle destination to hand off to the appropriate skill

Quick Start

Provide the approved intake route and run problem-framing to generate the problem-frame, options-brief, and design-direction.

Frequently Asked Questions about problem-framing

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

FAQPage Schema
How do I turn fuzzy intake into a crisp problem statement for stakeholders?

A problem-framing process converts an approved intake route into a structured problem-frame, generating a problem statement, target users, constraints, and assumptions to guide downstream discovery and design work.

What is an options-brief and when do I need it for requirements engineering?

An options-brief generates 2-3 viable design directions with trade-offs and recommended next steps. You need it during requirements engineering when an intake route is approved but requirements remain underspecified.

How do I generate decision-ready directions from underspecified requirements?

You generate decision-ready directions by applying problem-framing to an approved intake-brief, producing an options-brief and a recommended design-direction with clear inputs, outputs, and next-lifecycle guidance.

Can I use problem-framing without an approved intake-brief?

No, problem-framing requires an approved intake-brief as input. It is applied after intake when routing is clear, relying on this prerequisite to deliver a structured problem-frame and options-brief.

What's the best way to define non-goals and assumptions during product intake?

The best way to define non-goals and assumptions during product intake is to run a structured problem-framing step, which explicitly captures these elements alongside open questions to align stakeholders.