Finding Unknowns
Surface the gaps between what a task description says and what the work actually requires, before writing code. Use before implementing anything ambiguous, large, or unfamiliar; when the user asks "what am I missing", wants options or design directions, needs a mock or plan to react to, wants to be interviewed about a spec, is porting from a reference implementation, or gives a vague creative request they lack vocabulary for. Make sure to use this skill whenever the map (prompt/spec) might not match the territory (codebase/real requirements) — even if the user does not say "unknowns.
Install
npx skills add sidneyswift/skills --skill finding-unknownsgit clone --depth 1 https://github.com/sidneyswift/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/finding-unknowns ~/.claude/skills/finding-unknownsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Finding Unknowns
## Overview
The map is not the territory. The prompt, spec, and context are a map of the work; the codebase and the real requirements are the territory. Output quality is capped by how well the unknowns, the gaps between map and territory, get surfaced before implementation. Unaccounted unknowns fail both ways: the work quietly does the wrong thing, or it stalls on a question nobody asked. The cheapest place to find an unknown is before any code is written.
## The four quadrants
Classify what is known about the task, then pick the discovery move for the weak quadrant:
| Quadrant | What it is | Discovery move |
|---|---|---|
| Known knowns | Already in the prompt or spec | Nothing to do |
| Known unknowns | Open questions everyone is aware of | Ask directly: spec interview, options brainstorm |
| Unknown knowns | Context so obvious to the user they never wrote it down; they recognize it on sight | Give them something to react to: design directions, mocks, tweakable plans |
| Unknown unknowns | Traps nobody has considered | Go find them: blindspot pass, teach-me explainer, reference semantics map |
## Technique selection
| Situation | Technique | Reference |
|---|---|---|
| Implementing in an unfamiliar part of the codebase | Blindspot pass | references/blindspot-pass.md |
| The user lacks vocabulary for the domain ("make it nicer") | Teach-me explainer | references/teach-me-explainer.md |Details
- Skill name
finding-unknowns- Repository
- sidneyswift/skills
- Path
finding-unknowns/SKILL.md- Repo updated
- 9 November 2026
FAQ
What does the Finding Unknowns skill do?
Surface the gaps between what a task description says and what the work actually requires, before writing code. Use before implementing anything ambiguous, large, or unfamiliar; when the user asks "what am I missing", wants options or design directions, needs a mock or plan to react to, wants to be interviewed about a spec, is porting from a reference implementation, or gives a vague creative request they lack vocabulary for. Make sure to use this skill whenever the map (prompt/spec) might not match the territory (codebase/real requirements) — even if the user does not say "unknowns.
How do I install the Finding Unknowns skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add sidneyswift/skills --skill finding-unknowns. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Finding Unknowns popular?
It lives in sidneyswift/skills, which has 9 GitHub stars and 1 forks.
Related skills
Design Inspiration
9sidneyswift/skills
Break through design blocks by systematically mining curated inspiration sources. When you're stuck on UI, brand, layout, or visual direction, this skill walks you through nine high-signal design galleries — each covering a different design surface — to find patterns, steal structure, and restart your creative momentum. Use when someone is stuck, needs visual references, wants to explore design directions, or asks "what should this look like?
Design Visual Experiences
9sidneyswift/skills
Create or refine original digital visual experiences where art direction, motion, interaction, or spatial behavior is central. Use for expressive interfaces, interactive explainers, creative coding, and visual films; translate relevant references into implementation decisions and inspect the delivered result.
Ecosystem Mapping
9sidneyswift/skills
Take a core solution or transformation and map every friction point around it into a compounding product ecosystem — instead of building standalone products. Walks the user through identifying their core transformation, mapping friction points (before, during, after), spotting two-sided market opportunities, and designing products that strengthen each other. Use when someone has a working solution but is stuck on "what's next," wants to expand beyond a single product, or is thinking about leverage and ecosystem strategy.
Spec Goals
9sidneyswift/skills
Use when someone asks 'help me write a /goal', 'turn this into a goal', 'draft a goal for Codex', 'spec this for /goal', 'is this a good goal', or 'sharpen this objective'. Turns a defined, durable objective into a ready-to-paste Codex `/goal` with a measurable outcome, verification surface, constraints, boundaries, iteration policy, and blocked-stop condition. If the outcome, evidence, constraints, or approach still contains load-bearing unknowns, use flex-finding-unknowns first. Do NOT use this skill to execute the work.
Robodk Real Robot Control
9RoboDK/RoboDK-Agent-Skills
The ONLY skill in this repo allowed to move a real, physical robot — via robot.Connect() and RUNMODE_RUN_ROBOT/PROGRAM_RUN_ON_ROBOT, using RoboDK's robot drivers (Online Programming). Every other RoboDK skill here is simulation-only by design; redirect here the moment a request is unambiguously about the real robot moving, not the simulated one — phrasings like "move the real robot", "run this on the actual/physical robot", "connect to the robot and jog it", "online programming", "drive the robot live". Do not use for anything that stays in simulation, for generating a program to transfer late
Vscode Ready
9kargnas/skills
Use only when the user asks to set up VS Code/Cursor launch, debug, run, or tasks configs (e.g. "make this project VSCode-ready"). Do not run on your own.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.