agentleFS
Sign inStart free
ethosagentethosagent/ethos/skills/software-development/plan/SKILL.md

plan

Skill22 starsChanged 10 days agoMITView on GitHub

Render a long-form plan file in the standard Ethos shape (header, status, body, sequencing, acceptance gate, decisions log, session log). Companion to `writing-plans`, which loads alongside and supplies the spec the plan rendered against.

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 8 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

  • +1 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 167 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:

    Read related plans the new one cross-links to so the references are accurate (plan/phases/<existing>.md).

    line 49

“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

Drafts a structured plan file in the Ethos 7-section shape. This skill writes the file; the writing-plans companion supplies the conventions for what each section must contain.

When to use this skill

  • A change spans more than one PR or one author.
  • A change touches a frozen schema or a documented contract.
  • A change has trade-offs the team should debate before code lands.
  • The user asks for a plan, design doc, or proposal in the repo's standard format.

When NOT to use this skill

  • One-line fixes, typos, or local refactors. Just write the code.
  • Investigations that don't yet have a recommendation. Write a discovery note in the session log first.
  • Production incidents — write a runbook entry, not a plan.

Output shape

Plans live under plan/phases/<topic>.md (repo-scoped) or .ethos-work/plans/<slug>.md in the workspace (personal). File naming: snake_case for repo plans, kebab-case for personal. .ethos-work/ is the workspace's scratch directory, kept out of git by adding .ethos-work/ to .git/info/exclude. Personal plans do not go under ~/.ethos: a personality's default fs_reach lets write_file write only its own personality directory and its working directory (deriveFsReachPaths in packages/core/src/fs-reach.ts), so a write there is refused. The file must contain the seven sections the writing-plans companion specifies, in that order, with a Status legend at the top.

Workflow

  1. Confirm the plan target path with the user.
  2. Read related plans the new one cross-links to so the references are accurate (plan/phases/<existing>.md).
  3. Draft the seven sections. The body section can be deeply nested; everything else stays compact.
  4. Hand the draft back for review before any execution begins. Plans land via PR; execution follows in a separate PR keyed off the plan.

Anti-patterns

  • Mixing plan and execution in one turn — write the plan, stop, wait for review.
  • Acceptance gates without verifiable conditions ("ship when ready" is not a gate).
  • A decisions log entry without a rationale — the why is the artefact.

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