agentleFS
VladTheProgrammerVladTheProgrammer/claude-asimov/.claude/skills/facts/SKILL.md

facts

Skill0 starsChanged 4 months agoMITView on GitHub

Document how a conceptual area of the codebase is implemented with parallel sub-agents. Usage: /facts {concept} [hint paths...]

6 other projects use a version of this.

Adopted by

Most recently taken up by

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 4 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:

    Use the Agent tool with subagent_type: "fact-finder".

    line 20
  2. Distinctive:

    After the root agent completes, seed both lists from its response:

    line 28
  3. Distinctive:

    Add its COVERED items to covered

    line 29
  4. Distinctive:

    Add its SUGGESTED items to queue

    line 30
  5. Distinctive:

    If the filtered queue is empty, proceed to Phase 3.

    line 37
  6. Distinctive:

    After all agents in this round complete, for each agent:

    line 44
  7. Distinctive:

    Add its SUGGESTED items to queue (replacing the old queue)

    line 46
  8. Distinctive:

    After the loop exits:

    line 51
  9. Very specific:

    Use # {Concept} — Implementation Facts as the top heading

    line 56
  10. Distinctive:

    No frontmatter, no timestamps, no filler

    line 60
  11. Distinctive:

    Delete all fragment files

    line 61

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

Parse the user's input:

  • First argument is the concept (e.g., authentication, offline-sync, navigation)
  • Any additional arguments are hint file paths the agent should start exploring from

Phase 1 — Root exploration

Spawn a fact-finder agent with:

concept: {concept}
sub_area: {concept}
hints: {any hint paths provided, or "none"}

Use the Agent tool with subagent_type: "fact-finder".

Phase 2 — Recursive fan-out

Maintain two lists across rounds:

  • covered — all topics explored so far (accumulated from every agent's COVERED section)
  • queue — sub-areas to explore next

After the root agent completes, seed both lists from its response:

  1. Add its COVERED items to covered
  2. Add its SUGGESTED items to queue

Then loop:

  1. Filter the queue. For each proposed sub-area, evaluate:
    • Relevance: Is this sub-area meaningfully related to the original concept {concept}? Drop it if it has drifted to a tangential or generic topic.
    • Novelty: Has this topic (or something substantially overlapping) already been covered? Drop it if so.
  2. If the filtered queue is empty, proceed to Phase 3.
  3. Spawn one fact-finder agent per sub-area in the queue, all in parallel:
    concept: {concept}
    sub_area: {sub-area name}
    hints: {hints from the suggestion}
  4. After all agents in this round complete, for each agent:
    • Add its COVERED items to covered
    • Add its SUGGESTED items to queue (replacing the old queue)
  5. Go back to step 1.

Phase 3 — Merge & clean up

After the loop exits:

  1. Glob docs/{concept}/facts-*.md to find all fragment files
  2. Read every fragment
  3. Combine all fragments into docs/{concept}/facts.md:
    • Use # {Concept} — Implementation Facts as the top heading
    • Organize sections logically (root agent's broad content first, then deeper sub-area sections)
    • Deduplicate facts that appear in multiple fragments
    • Preserve all source file references
    • No frontmatter, no timestamps, no filler
  4. Delete all fragment files

Tell the user the output is at docs/{concept}/facts.md.

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.