Skip to content
Skills Library
Management & product · Planning

fog-explore

/fog-explore

Clear a map's Not yet specified: settle each open entry into a decision, a target update, an exclusion, or a hand-off to split, one entry at a time. Use when a map's next layer is blocked by an open entry.

Licence
Apache-2.0
Last repository change
13.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Clear a map's Not yet specified: settle each open entry into a decision, a target update, an exclusion, or a hand-off to split, one entry at a time. Use when a map's next layer is blocked by an open entry.

Original author description

Clear a map's Not yet specified: settle each open entry into a decision, a target update, an exclusion, or a hand-off to split, one entry at a time. Use when a map's next layer is blocked by an open entry.

How it works

  1. When it runs
  2. Steps
  3. Hands off
  4. What this skill does not do
Original SKILL.md headings · 32 lines, 419 words
SKILL.md preview
---
name: fog-explore
description: "Clear a map's Not yet specified: settle each open entry into a decision, a target update, an exclusion, or a hand-off to split, one entry at a time. Use when a map's next layer is blocked by an open entry."
family: track
invocation: model
---

# Fog explore

A map's `Not yet specified` holds fog. This skill clears it, one entry at a time, and writes the clearing itself: the entry struck through with what it became. What fog is, how an entry is written, and where a cleared entry lands are the `map` skill's; this file covers the clearing: how to judge an entry, how to get the missing part, and how to mark it finished.

## When it runs

The section holds an open entry and the next layer cannot be written without it. That is the whole trigger.

It ends when no open entry remains. When that happens, the map's next move is a split, not another round of exploring.

## Steps

Run these four for one entry, then start again at the top for the next.

1. **Judge.** Can this be settled now? An assumption someone has already tested, a fact one page answers, a decision with nothing missing — go to step 3. The rest go to step 2.
2. **Act.** Get the missing part: read, measure, or ask. A decision only a person can make goes through `grill-and-records`; the rounds go into a testimony as they happen. An answer that needs to be seen rather than discussed becomes a probe task, handed to `split`.
3. **Land it** where `map/res/body.md`'s landings send it: a decision to `Decisions so far`, a sharpened goal to `Target` and `Acceptance direction`, a refusal to `Out of scope`, work to a child through the action that opens that record. On a map that is open and has no children, this step writes the landing itself, by the section rule `map/res/body.md` gives every section. A map that is closed, or that has already split, has a body others stand on: its landing goes through `update`. An `Assumption` is not settled by research alone: support it, refute it, or record that it is accepted as reasonable and say so.
4. **Strike the entry through** and add `Resolved on <date>: <what it became and where>`. An entry that turned out to be irrelevant is deleted instead.

The entry is cleared and what it became is where `map/res/body.md`'s landings send it.

## Hands off

- `split` when no open entry remains, or when an entry became work.
- `update` for a landing on a map that is closed or has already split.
- `grill-and-records` for a decision the owner has to make.

## What this skill does not do

- Decide what a cleared entry becomes; `map/res/body.md` does.

Versions

The database has no other skills named fog-explore.

Database snapshot: 13.11.2026 · package version b5fdaa3782dd (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90open-map
    Write one map: turn the target it is given into a body with its fog and exclusions, and record where the target came from. The same action writes a root map and a child map. Use when a target is settled and has no map yet, or when a split is writing child maps.
  • 90cyc-explore
    Settle an open decision by comparing genuinely different options or building a throwaway prototype, then recommend one. Use when the user asks \"which approach\", \"what are my options\", or \"what should this look like\", when earlier options were rejected, or when a design…
  • 100pathfinder
    Map the fog of war before building. Given a project goal and known context, separate decisions already fixed from open decision frontiers and fog-of-war unknowns, tag each unknown with a next move (research, prototype, ask an expert, user test, or delegate), and lay out parallel…
  • 90split
    Turn a settled layer of a map into its next children: decide whether the layer is child maps or tasks, decide how many, and start each child through the action that writes it. Use when a map's layer is settled and its children do not exist yet.
  • 90decision-map
    When asked to chart a decision map, work a map ticket, or plan work whose open decisions gate each other, map the unresolved choices before build slices. Use for a new primitive, milestone charter, or integration that cannot yet be specified in one sitting.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.