explore-unknowns

Map task unknowns into four quadrants for structured analysis.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/2lab-ai/soma-work --skill explore-unknowns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explore-unknowns
Source: https://github.com/2lab-ai/soma-work/tree/main/src/local/skills/explore-unknowns
Command: npx skills add https://github.com/2lab-ai/soma-work --skill explore-unknowns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users understand and address unknown factors in tasks, improving planning and reducing surprises during implementation.

Core Features & Use Cases

  • Four-Quadrant Map: Identifies known knowns, known unknowns, unknown knowns, and unknown unknowns.
  • Interactive and Autonomous Modes: Supports interactive user input and autonomous pipeline execution.
  • Use Case: Use this Skill when beginning a new project where the scope or requirements are ambiguous or when working with a new codebase.

Quick Start

Run 'explore unknowns' to start the quadrant walk for task planning.

Frequently Asked Questions about explore-unknowns

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

FAQPage Schema
How do I identify unknown risks in project planning?

Identify unknown risks in project planning by mapping task scope using a four-quadrant approach that categorizes known knowns, known unknowns, unknown knowns, and unknown unknowns. This structured analysis reveals potential surprises before implementation begins.

What is the four-quadrant method for task analysis?

The four-quadrant method for task analysis is a structured mapping technique that categorizes project variables into known knowns, known unknowns, unknown knowns, and unknown unknowns to assess scope and reduce planning surprises.

Can I run risk assessment autonomously in automated pipelines?

Yes, you can run risk assessment autonomously in automated pipelines. The unknowns mapping supports both interactive user input for manual sessions and autonomous execution for continuous integration workflows.

When do I need to map unknowns for a new codebase?

You need to map unknowns for a new codebase when project scope or requirements are ambiguous. Use unknowns mapping at the beginning of implementation to perform structured analysis of task scope and potential risks.

What is the best way to assess task scope before implementation?

The best way to assess task scope before implementation is using a four-quadrant map to identify unknown factors. This approach distinguishes between known and unknown variables, improving planning accuracy and reducing unexpected issues.