agentleFS
alainatoralainator/worldcodex/.claude/skills/planning-worldbuilding/SKILL.md

planning-worldbuilding

Skill2 starsChanged 7 months agoMITView on GitHub

Decomposes a large worldbuilding task into a sequenced plan with concrete steps, target files, verification criteria, and dependency order. Use before building a new civilization, designing a planet, or any task spanning more than 3 files. Triggers on "plan this", "break this down", "how should we approach", "build plan for", or "what is the sequence". Does NOT write content — produces the plan only.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Does NOT write content (use /writing-science or /writing-worldbuilding).

    line 41
  2. Distinctive:

    Does NOT interrogate decisions (use /interrogating-design).

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Planning Worldbuilding

Break large worldbuilding tasks into sequenced, trackable steps.

When to Use

Any task that will produce more than 3 files.

Process

  1. Scope: Map files to create/modify, dependencies, existing constraints
  2. Write Plan: Save to meta/plans/YYYY-MM-DD-<topic>.md
  3. Review: Present for approval before writing

Task Design Rules

  1. Each task targets one file
  2. Tasks have verification criteria
  3. Dependencies are explicit
  4. Content is concrete (not "flesh out")
  5. YAGNI — if not needed for current scope, cut it

Checkpoint Pattern

For 5+ task plans, insert checkpoints every 3-5 tasks for author review.

Out of Scope

Does NOT write content (use /writing-science or /writing-worldbuilding). Does NOT interrogate decisions (use /interrogating-design).

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.