- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add dzhng/skills --skill explore-unknowns -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add dzhng/skills --skill explore-unknowns -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add dzhng/skills --skill explore-unknowns -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add dzhng/skills --skill explore-unknowns -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/dzhng/skills/tree/HEAD/skills/engineering/explore-unknownsFrom the publisher
The map is not the territory. The prompt, the plan, and the context window are the map; the codebase, the domain, and the user's actual intent are the territory. The gap between them is the unknowns — and an unknown found before code is written costs minutes, while the same unknown found three PRs later costs the three PRs.
This skill is a guided conversation: the quadrant walk. Together with the user you fill in a four-quadrant map of the task, one quadrant per stage, and the user walks away holding the completed map. The map is the deliverable; implementation is a different task that starts only after the map is handed over.
Two moves apply at every stage:
Five stages, walked in order, one at a time. When you enter a stage, read its reference file and follow it. Name the current quadrant as you go — the user should always know where they stand on the map — and finish the stage in front of you before opening the next.
When the user moves on to build, review, or merge what the walk mapped, read after the walk — the map lives on past planning.
Count questions the user has answered across the walk, not turns or answers found in the territory. After about five or six, if their preferences form a clear pattern and questions remain, pause the interview for this checkpoint. If the pattern is still unclear, continue targeted questions and offer once it becomes clear; do not manufacture questions just to reach the count.
Done when the user has chosen whether to delegate and, if opted in, the confirmed preferences and delegation scope are recorded alongside the map's decision ledger.
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time,
---name: explore-unknownsdescription: Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns…---# skills/engineering/explore-unknowns/SKILL.mdOverview
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the codebase or domain is unfamiliar, the user will "know it when they see it", a reference implementation must be understood before porting, mid-build deviations from the plan need capturing, or a finished change needs buy-in or verified understanding before merge. Pairs with [write-spec](../write-spec/SKILL.md) — walk the quadrants to burn off fog before slicing, and feed the finished map into the spec.
FAQ
Download skills/engineering/explore-unknowns/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/dzhng/skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.