agentleFS
ForgeyClapForgeyClap/Forge-Core/.claude/skills/forge-mindmap/SKILL.md

forge-mindmap

Skill2 starsChanged 5 days agoMITView on GitHub

Use when a plan reads better as a mind map (nodes and edges).

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Not needed for a trivial, single-path task.

    line 14
  2. Distinctive:

    Write the structure as an indented plain-text outline (2-space or tab indent = depth.

    line 17
  3. Distinctive:

    Real structure only: Every node reflects an actual part of the plan/architecture the Lead decided on — no filler branches, no invented …

    line 38
  4. Very specific:

    Secrets are auto-redacted: Every string in the map is redacted (forge-store.cjs's redactValue) before it is written to disk — never write a …

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Forge Mind Map (WP4)

A Forge mind map is a small node/edge graph — a root idea with branches and leaves — that the Lead generates to visualize a plan, an architecture, or a mission decomposition. It is built and stored by .claude/forge-bin/forge-mindmap.cjs, a zero-dependency writer that stores the structured JSON (and optional Mermaid/markdown sidecars) under .claude/forge-mindmaps/.

When the Lead generates one

  • To visualize a plan, architecture, or mission decomposition once it has real branching structure (a root idea with several sub-areas) — not for a flat 2-3 item list where prose is clearer.
  • Typically right after a Master Plan or Deep Learn Mode pass, so the map reflects real decisions already made, not a guess.
  • Not needed for a trivial, single-path task.

How

  1. Write the structure as an indented plain-text outline (2-space or tab indent = depth; the first line is the root):
    Mission Control Phase 2
      WP4 Mind Map
        Writer (forge-mindmap.cjs)
        Radial lens (dashboard)
      WP5 Next Work Package
  2. Build + store it:
    node .claude/forge-bin/forge-mindmap.cjs from-outline '<outline-text>' <map_id> --write --run <run_id> --mermaid
    • Omit --write to preview the parsed {nodes, edges} JSON without persisting anything.
    • --mermaid also writes a <map_id>.mmd Mermaid sidecar (graph TD, guarded — never crashes on odd input).
    • --run <run_id> logs mindmap_generated to that run's dashboard events — only fires once the map was actually written.
    • Already have a built {map_id, title?, nodes, edges} object instead of an outline? Use write directly: node .claude/forge-bin/forge-mindmap.cjs write '<map-json>' --write --run <run_id>.

What it produces

.claude/forge-mindmaps/<map_id>.json (the stored {map_id, title, nodes, edges, _generated}), optionally <map_id>.mmd (Mermaid) and <map_id>.md (nested outline), and an appended row in .claude/forge-mindmaps/index.jsonl. The dashboard's MIND MAP lens reads the latest stored map read-only and renders it as a root-centered radial graph (root at the center, branches/leaves on rings by depth, no node overlap).

Honesty rule (non-negotiable)

  • Real structure only. Every node reflects an actual part of the plan/architecture the Lead decided on — no filler branches, no invented depth just to make the map look bigger.
  • Secrets are auto-redacted. Every string in the map is redacted (forge-store.cjs's redactValue) before it is written to disk — never write a raw secret into a mind map.
  • The MIND MAP lens is read-only. There is no write endpoint on the dashboard for mind maps; the only way to create or change one is forge-mindmap.cjs write/from-outline. With no stored map yet, the lens shows an honest empty state — it never fabricates nodes.

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.