agentleFS
Sign inStart free
websublimewebsublime/mister-anderson/skills/plan/SKILL.md

plan

Skill3 starsChanged 7 months agoMITView on GitHub

Create a phase/feature plan that scopes work, defines high-level tasks, and identifies dependencies. Dispatches Ada for planning.

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

10 rules. 0 are common, 4 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a phase or feature plan that scopes work and identifies dependencies for research and specification.

    line 9
  2. Distinctive:

    If the user provides $ARGUMENTS, analyze them for:

    line 14
  3. Very specific:

    PRD must exist and be APPROVED: Ask the user for the PRD path (e.g., docs/PRD.md).

    line 20
  4. Very specific:

    Architecture doc should exist: Ask the user for the architecture path (e.g., docs/ARCHITECTURE.md).

    line 21
  5. Very specific:

    No PRD found. Recommend running /requirements first.

    line 25
  6. Very specific:

    No architecture doc found.

    line 29
  7. Distinctive:

    Ask the user: "What phase/feature is this plan for?" (e.g., "Phase 02 — MCP Complete")

    line 34
  8. Very specific:

    Ask for the phase number (e.g., 02)

    line 35
  9. Very specific:

    Ensure the docs/plans/ directory exists (create if needed)

    line 39
  10. Distinctive:

    Verify the plan file was created at the agreed path

    line 54

“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

Create a phase or feature plan that scopes work and identifies dependencies for research and specification.

<on-init> If the user provides $ARGUMENTS, analyze them for: - A phase number or feature name - Existing PRD/architecture paths </on-init><on-check> 1. **PRD must exist and be APPROVED.** Ask the user for the PRD path (e.g., `docs/PRD.md`). Read to confirm. 2. **Architecture doc should exist.** Ask the user for the architecture path (e.g., `docs/ARCHITECTURE.md`). </on-check><on-check-fail if="prd"> No PRD found. Recommend running `/requirements` first. </on-check-fail><on-check-fail if="architecture"> No architecture doc found. Warn that planning without architecture may lead to structural issues. Recommend running `/architecture` first, or proceed with caution. </on-check-fail><on-execute> 1. **Define phase scope:** - Ask the user: "What phase/feature is this plan for?" (e.g., "Phase 02 — MCP Complete") - Ask for the phase number (e.g., `02`)
  1. Define output location:
    • Suggest default: docs/plans/{NN}-plan-{feature-kebab}.md
    • Ensure the docs/plans/ directory exists (create if needed)

  2. Dispatch using exactly these parameters — no more, no less:

    Agent(
    subagent_type="architect",
    prompt="Create a PHASE PLAN (not a spec) for: {phase_description}. Read the PRD at {prd_path} and architecture at {arch_path} for context. This is a planning document that defines: scope (what's in/out for this phase), high-level task breakdown, dependencies between tasks, external dependencies and APIs that will need research, and acceptance criteria for the phase. Save to {plan_path} with status DRAFT. Do NOT write implementation specs — that comes after research validates the plan's assumptions. Iterate with the user until APPROVED."
)

    Do NOT add extra parameters unless the user explicitly requests it.

    </on-execute>
<on-complete> 1. Verify the plan file was created at the agreed path 2. Show the user the status from Ada's report (DRAFT or APPROVED) </on-complete><on-complete if="status=DRAFT"> Inform the user they can continue iterating with Ada. </on-complete><on-next> Recommend proceeding with `/research` to validate the plan's technical assumptions before creating the spec. </on-next>

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