agentleFS
matthewwong525matthewwong525/WongStack/.agents/skills/explore/SKILL.md

explore

Skill7 starsChanged 10 days agoMITView on GitHub

Think an idea through before planning: read the repo, run and try things, weigh options, clarify choices; changes no repo file.

67 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-context-isolation, agentica-infrastructure 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.

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 9 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 58 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start the change loop: compare options and settle scope before /plan.

    line 9
  2. Distinctive:

    Ask the shared way: two or three related ready choices, one if alone, within tool capacity.

    line 21
  3. Very specific:

    Update dependencies after answers or evidence.

    line 23
  4. Distinctive:

    The 80/20 test: ask where a wrong guess makes the plan *wrong*, not merely *different*: scope, observable behavior, compatibility, …

    line 25
  5. Distinctive:

    Before asking, recall the task and its likely paths once.

    line 29
  6. Distinctive:

    Treat dated facts as assumptions.

    line 36
  7. Distinctive:

    Separate parts?: Ask about a new workspace for each (how).

    line 57
  8. Distinctive:

    Answers open another choice?: Follow up; stop once none remains.

    line 58
  9. Distinctive:

    Keep an unanswered material preference open, never called an assumption or evidence gap.

    line 60
  10. Distinctive:

    Search memory and other work unless checked.

    line 72
  11. Distinctive:

    Run the exit round for open choices.

    line 73

“Common” is measured: kept by at least 6 in 10 of the 58 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

/explore

Start the change loop: compare options and settle scope before /plan. Find related work with openspec list --json and openspec context --json (CLI contract); read their pointers.

Change no repo file (limits); /plan logs answers. Explore precedes planning except review-page notes; use bounded mode under /plan. Standalone, run node .claude/skills/explore/scripts/step-title.mjs set EXPLORE --task "<the idea>".

Investigate the relevant flow

Read owning docs and source; trace trigger, result, and constraints. For non-code, read the process and authoritative sources. Separate observations from inferences. Run proportional, authorized checks: tests, scripts, builds; new code only in .scratch/. Report results before any plan; nothing outward. Name unavailable evidence and a later check.

For consequential choices, compare viable approaches, outcomes, costs; recommend with evidence. Before handoff, check material assumptions and failures against the flow; revise contradictions.

Questions during standalone exploration

Ask the shared way: two or three related ready choices, one if alone, within tool capacity. Track decisions and prerequisites in chat. Investigate a missing fact yourself; never ask the person to guess it.

Update dependencies after answers or evidence. Explain changed premises; reopen only affected decisions. Keep findings in chat, drawn as text when useful: chat shows no picture.

The 80/20 test: ask where a wrong guess makes the plan wrong, not merely different: scope, observable behavior, compatibility, acceptance criteria. Assume naming, placement, wording, and cheaply changed details, with reasons.

Search memory before asking

Before asking, recall the task and its likely paths once; read the originals cited:

node "$(git rev-parse --show-toplevel)/.claude/skills/memory/scripts/memory.mjs" recall <question>
node "$(git rev-parse --show-toplevel)/.claude/skills/memory/scripts/memory.mjs" areas <paths>

Treat dated facts as assumptions. Memory unavailable? Say so; continue with available sources.

Check for other work

For repo edits, check other work once:

node "$(git rev-parse --show-toplevel)/.claude/skills/explore/scripts/other-work.mjs"

Compare intent, not files: plans can overlap before edits.

  • Overlap: name the work and why; add the overlap ask to the next group, or ask alone.
  • No overlap: say nothing.
  • A notes line: say it in one line and continue.

The exit round

Resolve remaining material choices the shared way:

  • Apply 80/20 and tool capacity; ask only ready choices.
  • Separate parts? Ask about a new workspace for each (how).
  • Answers open another choice? Follow up; stop once none remains.
  • A settled choice stays settled, nested calls included.
  • Keep an unanswered material preference open, never called an assumption or evidence gap. Keep authorized defaults and the fallback when nobody can answer.

Summarize outcome, approach, reasons over a serious alternative, minor assumptions, and evidence limits.

  • Bounded: return by the steps below.
  • Standalone, typed by the person: offer next steps; only Plan it starts /plan.

When /plan invokes /explore

Planning uses bounded mode, including via /apply or /ship:

  1. Reuse the conversation's intent, answers, and findings.
  2. Search memory and other work unless checked; investigate only new material gaps.
  3. Run the exit round for open choices; await dependent answers, retaining authorized/unattended defaults.
  4. Return the summary to /plan.

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.