problem-space

Identify project objectives, constraints, and terrain into a Problem Space Map.

3|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/open-horizon-labs/skills --skill problem-space
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-space
Source: https://github.com/open-horizon-labs/skills/tree/main/problem-space
Command: npx skills add https://github.com/open-horizon-labs/skills --skill problem-space

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Map problem space before solving to ensure you understand objectives, constraints, and terrain before moving to solution space.

Core Features & Use Cases

  • Step 1: State the Objective Function
  • Step 2: Map the Constraints
  • Step 3: Identify the Terrain
  • Step 4: Surface Hidden Assumptions
  • Step 5: Check for X-Y Problems
  • Output: Produces a Problem Space Map including Objective, Constraints, Terrain, Assumptions, X-Y Check, Ready-for-Solution-Space indicator.

Quick Start

Invoke /problem-space to generate a structured problem space map for your current initiative.

Frequently Asked Questions about problem-space

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

FAQPage Schema
How do I frame a problem space before jumping into solutions?

Mapping a problem space requires identifying the objective function, constraints, and terrain to prevent premature solutioning. This formalization produces a Problem Space Map that surfaces hidden assumptions and checks for X-Y mismatches before entering the solution space.

What is an X-Y problem check in project planning?

An X-Y problem check in project planning identifies mismatches between your actual objective and the solution you are attempting to implement. It is a formal step in mapping the problem space to ensure you address the root problem, not just a proposed solution.

When should I map project constraints and terrain?

You should map project constraints and terrain at the start of work, when encountering blockers, or during patch-heavy iterations. Mapping these elements early prevents premature solutioning and clarifies the operational landscape before committing to a specific path.

How do I surface hidden assumptions in a project framework?

To surface hidden assumptions in a project framework, formalize your objective and constraints into a Problem Space Map. This structured mapping process explicitly highlights underlying assumptions and checks for X-Y mismatches before you transition into the solution space.

Does this problem mapping approach work for ongoing iterations?

Yes, this problem mapping approach works for ongoing iterations by applying the map during patch-heavy development cycles or when hitting blockers. It helps realign the objective and constraints to prevent compounding solutions on unverified assumptions.

What is the best way to prevent premature solutioning?

The best way to prevent premature solutioning is to map the problem space by defining the objective, constraints, and terrain first. Generating a Problem Space Map with an X-Y check ensures all assumptions are validated before entering the solution space.