Verified:GitHub

problem-definition

Define product or system problems with measurable success criteria and scope boundaries.

1|Updated Jan 22, 2026

Search Tags:#requirements #success criteria #product planning #problem definition #scope boundaries #decision boundaries #workflow gap

Ready to run

npx skills add https://github.com/Atlas-Memory-Framework/AtlasMemory-Tools --skill problem-definition-atlas-memory-framework

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: problem-definition
Source: https://github.com/Atlas-Memory-Framework/AtlasMemory-Tools/tree/main/.cursor/skills/problem-definition
Command: npx skills add https://github.com/Atlas-Memory-Framework/AtlasMemory-Tools --skill problem-definition-atlas-memory-framework

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps clarify the real product or system gap behind a request, so future work is grounded in measurable outcomes and explicit boundaries rather than assumptions.

Core Features & Use Cases

Measurable problem framing: produces a structured problem narrative with success criteria that can be verified.
Workflow gap articulation: captures current broken workflow vs desired workflow and why the gap matters now.
Scope discipline: defines in-scope vs out-of-scope, constraints, glossary terms, and open questions.
Decision boundaries: includes A/B/C fork guidance when applicable so follow-on work stays coherent.

Quick Start

Ask the orchestrator to run problem-definition at the start of your planning flow or when you need to define the problem, and provide any relevant repo/user context so it can produce the required section content.

Frequently Asked Questions about problem-definition

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

FAQPage Schema

How do I turn vague product goals into measurable success criteria?▼

To turn vague product goals into measurable success criteria, you need a structured problem definition that captures the workflow gap, defines testable outcomes, and sets explicit scope boundaries before downstream planning begins.

What is problem definition in product planning and when should I use it?▼

Problem definition in product planning is the process of articulating the real system gap behind a request with measurable outcomes. Use it at the start of plan generation before ideation or technical planning loops to ground future work.

How do I define scope boundaries and decision forks for a new system requirement?▼

Defining scope boundaries and decision forks requires separating in-scope from out-of-scope items, listing constraints, and adding A/B/C fork guidance so follow-on technical planning stays coherent within the established decision boundaries.

Can I articulate a broken workflow gap before starting technical planning?▼

Yes, you can articulate a broken workflow gap before technical planning by documenting the current workflow versus the desired workflow and explaining why closing that gap matters now, producing a structured draft validated against evidence-based gates.

What's the best way to structure a problem statement for downstream implementation?▼

The best way to structure a problem statement for implementation is producing a draft section with required fields like glossary terms and open questions, validated for completeness against evidence-based gates before returning it for downstream planning.

Why does my product planning loop lack decision boundaries and testable scope?▼

Your product planning loop lacks decision boundaries and testable scope when the initial problem definition skips measurable success criteria and explicit in-scope versus out-of-scope constraints, allowing assumptions to drive implementation.