agentleFS
Sign inStart free
HazATHazAT/pi-config/skills/plan/SKILL.md

plan

Skill451 starsChanged 7 months agoMITView on GitHub

Interactively investigate a request, compare approaches, and write the selected implementation plan to a supplied Markdown path. Use for planning, brainstorming, or exact /plan.

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 164 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:

    Clarify: ask only questions whose answers materially change the design.

    line 14
  2. Distinctive:

    Select: ask the user to choose or approve an approach.

    line 16
  3. Distinctive:

    Write: after selection, resolve routine details from evidence and write only the absolute plan path supplied by the caller.

    line 17
  4. Distinctive:

    Keep each interactive turn focused.

    line 19
  5. Distinctive:

    Use objective acceptance criteria and name important wrong approaches.

    line 65

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

Plan in the current chat. Do not implement, create todos, review, or launch source-writing agents.

Workflow

  1. Investigate: inspect repository instructions, Git state, relevant files, tests, and existing patterns. Ground claims in what you read.
  2. Confirm intent: summarize the requested outcome, implicit requirements, boundaries, and the most important success condition. Ask for corrections.
  3. Clarify: ask only questions whose answers materially change the design. Resolve observable behavior, edge cases, quality level, and explicit exclusions.
  4. Compare approaches: present 2–3 materially different options with tradeoffs, risks, effort, and a recommendation.
  5. Select: ask the user to choose or approve an approach. Do not write the plan before this checkpoint.
  6. Write: after selection, resolve routine details from evidence and write only the absolute plan path supplied by the caller. Stop.

Keep each interactive turn focused. Investigate facts instead of asking the user to provide facts available in the checkout.

Plan Format

# [Plan name]

**Status:** Ready
**Request:** [one sentence]
**Selected approach:** [one sentence]

## Intent

## Scope

### In scope
- ...

### Out of scope
- ...

## Acceptance Criteria
- [ ] ISC-1: [binary, observable criterion]
- [ ] ISC-2: ...

## Repository Evidence
- `path:line` — [relevant fact or convention]

## Approaches Considered

### Selected: [name]
[Why it best fits]

### Rejected: [name]
[Tradeoff that ruled it out]

## Implementation
1. [ordered change with files/components]

## Verification
- `[command]` — [what it proves]

## Assumptions and Risks
- [assumption or failure mode] — [mitigation or accepted risk]

Use objective acceptance criteria and name important wrong approaches. Do not create a sidecar directory, run record, todo file, review file, or custom state.

Download now (ZIP)

  • Other versions182 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 182

    1. Yeachan-Heo/oh-my-codex★ 34ksame name
    2. crbnos/carbon★ 2.8ksame name
    3. graphistry/pygraphistry★ 2.6ksame name
    4. zereight/gitlab-mcp★ 2.1ksame name
    5. math-inc/OpenGauss★ 1.3ksame name
    6. fuyuxiang/echo-agent★ 1.1ksame name
    7. kdlbs/kandev★ 1ksame name
    8. suboss87/FDEOps★ 940same name
    9. loongclaw-ai/loongclaw★ 640same name
    10. witnesstodark/mr-mak-workspace★ 609same name

    172 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use webhook-subscriptions, 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.
    • 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

      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

    • 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

    • ibahgatSkill

      context-optimize

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

      Also in 3 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

    • +4 more from math-inc
  • In this repository14 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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