unknowns-mapper

Separates knowns, unknowns, assumptions, and risks into an Unknowns Map with research paths and stopping rule.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/ThorStarlord/interface-skills --skill unknowns-mapper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unknowns-mapper
Source: https://github.com/ThorStarlord/interface-skills/tree/main/skills/unknowns-mapper
Command: npx skills add https://github.com/ThorStarlord/interface-skills --skill unknowns-mapper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

unknowns-mapper separates what is known from what is missing or assumed so teams can avoid premature implementation when starting a project.

Core Features & Use Cases

  • Unknowns Map output: Produces a structured breakdown of Knowns, Unknowns, Assumptions, Risks, Research Paths, and a Stopping Rule to support safe decision-making.
  • Problem-frame intake mapping: Classifies information gaps against a given problem frame or repository goal to clarify what must be resolved next.
  • Research path definition (no execution): Defines time-boxed research paths that convert unknowns/assumptions into knowns while explicitly preventing the skill from doing the research itself.

Use case example: When onboarding to a new repository, you need to figure out what requirements and constraints are unclear before planning implementation, so the map guides where to investigate and when to stop.

Quick Start

Use the unknowns-mapper skill by providing the project goal and asking it to produce an Unknowns Map that includes knowns, unknowns, assumptions, risks, research paths, and a stopping rule.

Frequently Asked Questions about unknowns-mapper

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

FAQPage Schema
How do I separate known facts from unknowns and assumptions during project kickoff?

To separate knowns from unknowns during project kickoff, generate an Unknowns Map that classifies information gaps against your repository goal to clarify what must be resolved before implementation. This structured breakdown identifies knowns, unknowns, assumptions, and risks.

What is an unknowns map and when do I need one for requirements discovery?

An unknowns map is a structured breakdown of knowns, unknowns, assumptions, risks, research paths, and a stopping rule. You need one for requirements discovery during early-stage project initiation to avoid premature implementation when information is missing.

How do I define research paths and a stopping rule for risk assessment?

Define time-boxed research paths and a stopping rule by mapping assumptions and unknowns against a problem frame. This converts unknowns into knowns for risk assessment while explicitly preventing the execution of the research itself.

Can I use this approach to plan research before onboarding to a new repository?

Yes, you can use this approach to plan research before onboarding to a new repository. By classifying information gaps against the repository goal, it guides where to investigate requirements and constraints and defines exactly when to stop.

Does the unknowns mapping process actually perform the research it defines?

No, the unknowns mapping process does not perform the research it defines. It strictly separates knowns from unknowns to produce a research plan with defined paths and a stopping rule, explicitly preventing the skill from doing the research itself.