agentleFS
nearmapnearmap/shipyard/skills/plan/SKILL.md

plan

Skill1 starsChanged 21 days agoMITView on GitHub

Turn a large objective or existing Epic into a living roadmap with a configured cap (plan.max_active_tasks) of active /sy:spec-ready Tasks, real seams, dependency order, and flat tracker execution.

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

4 rules. 0 are common, 1 is distinctive, and 3 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before anything else — before this turn spends any research — run the tracker preflight …

    line 16
  2. Distinctive:

    Not every issue surfaced mid-ship earns its own leaf: a small, adjacent, low-risk fix folds into the current PR as a recorded scope …

    line 26
  3. Very specific:

    When every horizon is delivered and every child is done for delivered reasons, set the Epic done.

    line 58
  4. Very specific:

    Every subagent dispatch resolves its model and effort from config and passes them as the Agent invocation's actual model and effort …

    line 60

“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

Build or revise one living Epic roadmap. The Epic body owns conceptual depth; executable Tasks/Bugs remain direct children. End at the roadmap and /sy:spec handoffs. Never implement or spec leaves.

Plan against fresh origin/main unless the user names another base. Work code read-only. Tracker writes use the tracker skill (/sy:tracker).

Before anything else — before this turn spends any research — run the tracker preflight (${CLAUDE_PLUGIN_ROOT}/skills/shared/references/preflight.md). A failure stops here with its single ## Action needed block, not partway through the roadmap.

$ARGUMENTS

Invariants

  • Work backwards: North Star → capabilities → dependency order → near executable leaves.
  • Premise + prior-work check comes first: before shaping, validate the objective's premise and search for existing, shipped, duplicate, or sibling work (tracker find-issues plus a code/PR search); prior delivery or duplication reshapes or ends the roadmap rather than re-planning it.
  • At most the resolved plan.max_active_tasks cap of leaves may be active /sy:spec-ready/in-spec/in-ship/in-review at once — resolve per ${CLAUDE_PLUGIN_ROOT}/skills/shared/references/config-values.md.
  • One Task/Bug ≈ one coherent PR. Keep far work conceptual until evidence justifies decomposition.
  • Not every issue surfaced mid-ship earns its own leaf: a small, adjacent, low-risk fix folds into the current PR as a recorded scope extension, and a follow-up must justify itself against that (see ${CLAUDE_PLUGIN_ROOT}/skills/shared/references/scope-discipline.md).
  • Objective is stable; path is provisional and should adapt to shipped evidence.
  • Flat tracker execution, fractal conceptual map.
  • Ask through AskUserQuestion only when the answer changes seam, sequence, blocker, or outcome — see ${CLAUDE_PLUGIN_ROOT}/skills/shared/references/user-interaction.md. At an approval point that authorizes tracker writes, name the mutations the go-ahead covers — create/edit the Epic, create/edit its children, and post the plan checkpoint — so auto-mode consent is informed rather than a bare "proceed".

Scope and delegation

Read small cohesive evidence directly. Use sy:sweep for large code/ticket/PR/docs surfaces and sy:seam only for one unresolved boundary that changes roadmap shape. At most the resolved limits.max_depth_agents cap in flight — resolve per ${CLAUDE_PLUGIN_ROOT}/skills/shared/references/config-values.md. Agent returns are compressed leads; verify decisive spans and own the cut.

Read durable cross-session memory early — memory_list (or memory_search on the tools/surfaces the objective touches) per ${CLAUDE_PLUGIN_ROOT}/skills/shared/references/memory.md; a lesson that bears on the objective enters the brief as a known anchor, and a lesson this objective's own research directly contradicts is refuted immediately (memory_refute, same reference) rather than carried forward or silently dropped.

Seed every agent prompt with known anchors — paths, symbols, entry points, keys — and name ground already covered; agents must not rediscover what the caller knows.

Machine-facing agent briefs stay pointer-dense. Human-facing Epic maps and decision logs remain clear prose. Both, and the roadmap and # SEAMS comments this skill posts, are written under ${CLAUDE_PLUGIN_ROOT}/skills/shared/references/context-economy.md.

State router

Classify before loading detailed procedure:

NEW       objective, no Epic yet        → references/new-objective.md
REENTRY   existing Epic                 → references/reentry.md
SHAPING   evidence gathered             → references/roadmap-shaping.md
CAPTURE   roadmap decisions settled     → references/checkpoint-handoff.md

Load only the reference for the current state. Do not preload mutually exclusive procedures.

Completion bar

The Epic body must show North Star, conceptual horizon ladder, completed branches, current active set (≤ the resolved plan.max_active_tasks cap) with keys/kickoffs, queued conceptual work, critical path, blockers, and parallel-safe set. Every planning run that changes the tracker adds one decision-log delta ending in a Plan checkpoint footer. A roadmap entry or checkpoint that shipped evidence later overrules is corrected on its own surface, not left stale — the retroactive-honesty invariant in ${CLAUDE_PLUGIN_ROOT}/skills/shared/references/write-integrity.md.

When every horizon is delivered and every child is done for delivered reasons, set the Epic done.

Every subagent dispatch resolves its model and effort from config and passes them as the Agent invocation's actual model and effort parameters, per ${CLAUDE_PLUGIN_ROOT}/skills/shared/references/model-dispatch.md; a nested dispatch inherits nothing and must resolve again.

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.