agentleFS
Sign inStart free
adventurewave-labsadventurewave-labs/apsl-core/skills/plan/SKILL.md

plan

Skill0 starsChanged 4 months agoMITView on GitHub

Generate an explicit step-by-step plan before taking action. Use before complex, multi-step, or risky tasks to enforce think-before-act discipline. After presenting the plan, request a halt and wait for approval.

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

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

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 1

    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:

    Do not proceed until explicit approval is given.

    line 63

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

Core rule: Present the plan. Then request a halt. Never begin execution without approval.

Execution Steps

  1. Load context — read CLAUDE.md, GEMINI.md, AGENTS.md, README, or relevant docs.
  2. Understand the goal from the provided context.
  3. Think through the problem — unknowns, failure modes, dependencies.
  4. Generate a numbered plan:
## Plan: <goal>

### Steps
1. [LOW RISK] Description of step one
   - What: specific action
   - Files affected: list
   - Reversible: yes/no

2. [MED RISK] ...

⏸ CHECKPOINT — Recommend human review before step N (reason: ...)

N. [HIGH RISK] Final step

### Dependencies
- Step 3 requires Step 2 to complete successfully

### Risks
- If step 4 fails: fallback is ...
  1. Request a halt — display:
─────────────────────────────────
⏸ PLAN COMPLETE — AWAITING APPROVAL
─────────────────────────────────
Reply "approved" or "go" to begin execution,
or describe modifications to the plan.
─────────────────────────────────
  1. Do not proceed until explicit approval is given. Treat any non-approval response as a modification request.

Note: Steps 5–6 describe requested behavior. Actual halting is not guaranteed by this skill; pair with the agent's native permission controls for hard gating.

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