agentleFS
jpc4729jpc4729/setup/skills/my-skills/wayfinder/SKILL.md

wayfinder

Skill0 starsChanged 6 days agoMITView on GitHub

Charts an idea too big for one session as a map of open decisions in a local file, then resolves one decision per session until the way to the goal is clear.

195 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-ts-deep-modules, to-questionnaire and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 42 projects that use this

  • AWSSkill

    to-questionnaire

    Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

    Also in 87 projects that use this

  • AWSSkill

    wizard

    Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

    Also in 124 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 50 projects that use this

  • LesaniSkill

    writing-beats

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

    Also in 54 projects that use this

  • ryotaroh180105Skill

    claude-handoff

    Hand the current conversation off to a fresh background agent that picks up the work immediately.

    Also in 40 projects that use this

  • +2 more from aws

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 179 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If no fog remains and the work fits one session, say so and stop.

    line 56
  2. Distinctive:

    Write the map. Leave Decisions empty.

    line 57
  3. Distinctive:

    Stop; charting resolves nothing.

    line 58
  4. Very specific:

    Read the map. Without a path, use the only map in ~/.local/state/maps/<repo>/, or ask which one when there are several.

    line 62
  5. Distinctive:

    Update the map: add new precise questions to Open.

    line 66
  6. Very specific:

    Stop after one question; research questions are the exception.

    line 67
  7. Very specific:

    When Open and Fog are empty, the way is clear.

    line 69

“Common” is measured: kept by at least 6 in 10 of the 179 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Wayfinder

Find the way to a goal that is too big and too unclear for one session. Decide; do not build. The map is done when nothing is left to decide before the work starts. When you want to start the work, the map is probably done.

The map

One file outside the repository, so nothing commits it: ~/.local/state/maps/<repo>/<slug>.md. <repo> is the repo root's folder name without a leading dot; <slug> is two or three words from the idea.

# Map: <slug>

Goal: <what done looks like: a spec, a decision or a change; 2 lines at most>
Notes: <constraints, sources to read, standing preferences>

## Decisions

- Q<n> <question>: <answer, one line>. Evidence: <path:line, URL, or the user and the date>

## Open

- Q<n> <question>: <ask | research | try | task>, after: <Q numbers, or none>

## Fog

- <a question you can see coming but cannot yet state precisely>

## Out of scope

- <work past the goal>: <why>
  • A question goes to Open when you can state it precisely now, even if it waits on another question. Otherwise it goes to Fog, as loosely as you see it. Keep fog coarse: one patch can become several questions, or none.
  • Each decision lives in one place. An answer longer than one line goes to <slug>/Q<n>.md beside the map, linked from its decision line.
  • To the user, name a question by its words, not only by its number.

Question types

  • ask: only the user can decide. Ask one question at a time, with the options, the evidence and your pick. Never answer for the user.
  • research: a fact from code, docs, data or the web. Find it yourself and record the source.
  • try: the question is how something looks or behaves. Make a cheap, rough sample (a sketch, a stub, a sample output) under one mktemp -d directory, show it, and let the user decide.
  • task: a step that must happen before a decision, such as access, an account or sample data. Do it when you can; else give the user numbered steps. Record what was done and the facts that later questions need.

Chart (argument: an idea)

  1. Settle the goal with the user first; it sets the scope.
  2. List the open decisions across the whole idea, broad before deep. Research what a read can answer before you ask.
  3. If no fog remains and the work fits one session, say so and stop. No map.
  4. Write the map. Leave Decisions empty.
  5. Stop; charting resolves nothing. Report the map path and the first open questions.

Work (argument: a map path, optional question)

  1. Read the map. Without a path, use the only map in ~/.local/state/maps/<repo>/, or ask which one when there are several.
  2. Take the question the user names, else the first one in Open whose after questions are all decided and that no other session marked taken. Mark it taken before you start.
  3. Resolve it by its type.
  4. Move it to Decisions with its answer and evidence.
  5. Update the map: add new precise questions to Open; move fog that is now precise to Open and delete it from Fog; move work past the goal to Out of scope with the reason; change or delete each question the answer makes wrong.
  6. Stop after one question; research questions are the exception. Report the decision and the next open question.

When Open and Fog are empty, the way is clear. Say so, and name the next step: the work itself, or the planner, with this map's path, for more than one sitting. Delete the map only when the user asks.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.