unknown

Identify hidden assumptions in strategy documents using Known/Unknown quadrant analysis.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/seungwonme/.claude --skill unknown
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unknown
Source: https://github.com/seungwonme/.claude/tree/main/skills/clarify/unknown
Command: npx skills add https://github.com/seungwonme/.claude --skill unknown

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Surface blind spots and hidden assumptions in strategy, plan, or decision documents using the Known/Unknown quadrant framework and hypothesis-driven questioning.

Core Features & Use Cases

  • Four-quadrant classification (KK, KU, UK, UU) to surface unknowns and knowns
  • Hypothesis-driven questioning with structured options
  • 3-round depth pattern: R1 validation, R2 deep dive, R3 execution details
  • Built-in playbook templates and reference materials
  • Use cases: strategy reviews, risk assessment, project planning

Quick Start

Paste or upload your strategy document to kick off a Known/Unknown quadrant analysis.

Frequently Asked Questions about unknown

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

FAQPage Schema
How do I find hidden assumptions in a strategy document?

You can surface blind spots in a strategy document by applying the Known/Unknown quadrant framework, which classifies information into known-knowns, known-unknowns, unknown-knowns, and unknown-unknowns to expose hidden assumptions.

What is the Known/Unknown quadrant framework for risk assessment?

The Known/Unknown quadrant framework is a strategy analysis method that classifies project information into four quadrants—KK, KU, UK, and UU—to systematically identify unknowns and hidden assumptions during risk assessment.

How do I apply hypothesis-driven questioning to project planning?

Apply hypothesis-driven questioning to project planning by following a 3-round depth pattern: round one validates assumptions, round two executes a deep dive, and round three focuses on execution details across all four Known/Unknown quadrants.

Does this strategy analysis approach require any specific dependencies?

No dependencies are required to use this strategy analysis approach. You can paste or upload your strategy document directly to kick off the Known/Unknown quadrant analysis without external tools or plugins.

What are the limitations of using quadrant analysis for strategy reviews?

Limitations of quadrant analysis include strict guardrails around question design and playbook output, requiring explicit stop conditions and success criteria to prevent unstructured exploration during strategy reviews.