agentleFS
kapadiaskapadias/nonna/.claude/skills/plan/SKILL.md

plan

Skill0 starsChanged 46 days agoMITView on GitHub

Turn a request into a written plan — restate requirements, surface risks, decompose into reviewable steps, and identify the gates each step must pass.

184 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use context-optimize, heartmula 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.
  • SireJeffSkill

    context-optimize

    Context Optimization - Orchestrate RPI workflow TODO generation with interactive scoping

    Also in 4 projects that use this

  • 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

  • +3 more from math-inc

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    Write it down: if it spans more than one module — a short plan in the PR description or docs/.

    line 24

“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 the work for: $ARGUMENTS

Steps

  1. Restate the requirement in your own words. State what "done" means concretely and what is explicitly out of scope. If the request is ambiguous in a way that changes what gets built, ask before planning further.
  2. Research & reuse first. Rung 1 of the ladder: does it need to exist at all? Name the lazier alternative in one line before planning the full version. Then search the codebase for the existing pattern to match, and the ecosystem for a library that already solves ≥80% of this. Note what you will reuse rather than build. Use explorer for the codebase sweep so this thread stays lean.
  3. Surface risks and unknowns. What could break? What is irreversible or outward-facing (see .claude/rules/safety.md)? What touches a trust boundary (see .claude/rules/boundaries.md)? How will you know if it went wrong?
  4. Decompose into reviewable steps. Each step is small, independently testable, and ordered by dependency. For each, name the test that will pin it and the gate it must pass.
  5. Write it down if it spans more than one module — a short plan in the PR description or docs/. A plan that fits in your head can stay there; one that doesn't goes on disk.

Output

A numbered plan: steps, the test for each, the risks, and what is reused vs. built. End with the first concrete action and which agent/command runs it (typically /tdd).

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.