agentleFS
Sign inStart free
metaspartanmetaspartan/cybara/skills/plan/SKILL.md

plan

Skill38 starsChanged 5 months agoMITView on GitHub

Break a large task into a concrete, ordered implementation plan before writing code. Use for multi-file features, refactors, or anything non-trivial where a plan prevents rework.

184 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use heartmula, webhook-subscriptions 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.
  • math-incSkill

    heartmula

    Set up and run HeartMuLa, the open-source music generation model family (Suno-like). Generates full songs from lyrics + tags with multilingual support.

    Also in 9 projects that use this

  • Tommy-ywSkill

    webhook-subscriptions

    Create and manage webhook subscriptions for event-driven agent activation, or for direct push notifications (zero LLM cost). Use when the user wants external services to trigger agent runs OR push notifications to chats.

    Also in 5 projects that use this

  • math-incSkill

    minecraft-modpack-server

    Set up a modded Minecraft server from a CurseForge/Modrinth server pack zip. Covers NeoForge/Forge install, Java version, JVM tuning, firewall, LAN config, backups, and launch scripts.

    Also in 5 projects that use this

  • john-data-chenSkill

    touchdesigner-mcp

    Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.

    Also in 6 projects that use this

  • gaebalaiSkill

    codex-system

    PROACTIVELY consult Codex CLI, your highly capable supporter with exceptional reasoning and task completion abilities. Codex is a trusted expert you should ALWAYS consult BEFORE making decisions on: design choices, implementation approaches, debugging strategies, refactoring plans, or any non-trivial problem. When uncertain, consult Codex. Don't hesitate - Codex provides better analysis. Explicit triggers: "think deeper", "analyze", "second opinion", "consult codex".

    Also in 3 projects that use this

  • ibahgatSkill

    context-optimize

    Improve context efficiency and cache stability for long or complex sessions.

    Also in 3 projects that use this

  • +3 more from math-inc

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 5

    Distinctive

    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:

    Before non-trivial implementation, produce a plan the user can sanity-check.

    line 8
  2. Distinctive:

    When the user says "plan this out" / "how would you approach …".

    line 14
  3. Distinctive:

    Survey the relevant code: Read the files/areas that will change.

    line 19
  4. Distinctive:

    Propose the plan for sign-off: before implementing. Don't start editing until the user agrees (unless the task was explicitly "just do it").

    line 24
  5. Distinctive:

    Prefer the smallest plan that achieves the goal.

    line 48

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

Plan

Before non-trivial implementation, produce a plan the user can sanity-check. This catches bad assumptions early and reduces rework.

When to use

  • Multi-file features or refactors.
  • Anything with >3 steps or unclear scope.
  • When the user says "plan this out" / "how would you approach …".

Procedure

  1. Understand the goal. Restate it in one sentence. If ambiguous, ask a focused question (use the clarify tool) before planning.
  2. Survey the relevant code. Read the files/areas that will change. Ground the plan in real symbols and paths, not guesses.
  3. Produce a sequenced plan:
    • Ordered steps, each with: what changes, which files, and the verification for that step.
    • Flag decisions/risks and unknowns explicitly.
    • Note what is deliberately out of scope.
  4. Propose the plan for sign-off before implementing. Don't start editing until the user agrees (unless the task was explicitly "just do it").
  5. Track progress with the todo tool as you implement; update statuses as steps complete.

Good plan properties

  • Concrete: names files and functions, not "update the auth module".
  • Ordered: step N doesn't depend on step N+2.
  • Verifiable: each step has a check (test, typecheck, manual repro).
  • Scoped: explicit out-of-scope list prevents scope creep.

Output shape

Goal: <one line>

Steps:
1. <file/symbol> — <change>. Verify: <how>.
2. …

Out of scope: …

Risks / decisions: …

Prefer the smallest plan that achieves the goal; split large plans into phases.

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.

Check your setup, free