problem-framing

Runs a socratic intake to produce a five-field BRIEF.md before task creation.

6|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/Mozurok/fhorja.dev --skill problem-framing-mozurok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: problem-framing
Source: https://github.com/Mozurok/fhorja.dev/tree/main/.claude/skills/problem-framing
Command: npx skills add https://github.com/Mozurok/fhorja.dev --skill problem-framing-mozurok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often start AI-assisted work on a fuzzy, broad, or mis-scoped objective, and every downstream decision inherits that bad framing. This Skill questions whether the stated problem is the right problem before any task folder exists, then captures the result in a reviewed BRIEF.md that task-init consumes. ## Core Features & Use Cases - Socratic intake: Asks one clarifying question at a time, preferring multiple choice, to shape the objective before any task memory is created. - Five-field BRIEF.md: Produces a problem statement, success criteria, non-goals, a recommended approach from 2-3 candidates with trade-offs, and named deliverables. - Spec-file intake: Reads a supplied spec or PRD with a definition-completeness reader, pre-filling brief fields with named sources and asking only about partial or missing fields. - Use Case: A user says "we should rebuild the onboarding flow." The Skill interviews them, discovers the real problem is activation drop-off at step two, and writes a brief that task-init turns into a properly scoped task. ## Quick Start Ask the assistant to run problem-framing on your rough objective or idea before creating any task, and answer its questions one at a time until it writes BRIEF.md.

Frequently Asked Questions about problem-framing

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

FAQPage Schema
How do I scope a vague feature idea before starting a task?▼

Run problem-framing on the rough objective. It asks one clarifying question at a time, proposes 2-3 approaches with trade-offs, and writes a five-field BRIEF.md that task-init consumes to seed the new task.

What goes into the BRIEF.md file it produces?▼

The brief has exactly five fields: a one-sentence problem statement, measurable success criteria, non-goals, a recommended approach chosen from 2-3 candidates, and named deliverables. It stays under one page and is moved into the task folder by task-init.

When should I not use problem-framing?▼

Skip it when the objective is already specific enough to state in one sentence, for bug fixes or hotfixes, when a decision is needed inside an existing task, or when an active task already exists. In those cases it returns a NO_OP routing to task-init or what-next.

Can problem-framing read an existing spec or PRD?▼

Yes. When you supply a spec file, it runs a definition-completeness reader that reports each criterion as present, partial, or missing with named sources. Pre-filled fields still require your confirmation, and missing fields become questions.

Does problem-framing work without a human answering questions?▼

In unattended runs it does not invent answers. It fills fields supplied by the dispatching brief with a provenance note and marks everything else as explicit NEEDS CLARIFICATION markers, which task-init consumes with the gaps visible.