agentleFS
Sign inStart free
codebycoreycodebycorey/delta-spec/skills/plan/SKILL.md

plan

Skill4 starsChanged 9 months agoMITView on GitHub

Create design and delta specs from a proposal. Use when planning implementation, exploring codebase for approach, or creating a design.

We split this skill into the rules it gives an agent

9 rules. 0 are common, 4 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 162 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a design document and delta specs based on the proposal and codebase exploration.

    line 8
  2. Very specific:

    Arguments: If $ARGUMENTS is provided, use it as the name parameter.

    line 10
  3. Very specific:

    Read proposal.md to understand problem/scope

    line 22
  4. Very specific:

    Read design.md if it exists (for refinement)

    line 23
  5. Distinctive:

    Read existing delta specs if any

    line 24
  6. Distinctive:

    If unsatisfied dependencies exist:

    line 30
  7. Very specific:

    Create delta specs in specs/.delta/<name>/specs/<domain>.md

    line 59
  8. Very specific:

    Use the delta format (ADDED/MODIFIED/REMOVED sections)

    line 60
  9. Distinctive:

    If main spec doesn't exist yet, note it will be created

    line 61

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

/ds:plan [name] - Create design and delta specs

Create a design document and delta specs based on the proposal and codebase exploration.

Arguments: If $ARGUMENTS is provided, use it as the name parameter. Otherwise, follow the determination logic below.

Step 0: Version Check

See version-check.md for the standard version compatibility check procedure.

Step 1: Determine which change

See determine-change.md for the standard change resolution procedure. Prerequisite: suggest /ds:new.

Step 2: Build context

  • Read proposal.md to understand problem/scope
  • Read design.md if it exists (for refinement)
  • Read existing delta specs if any

Step 3: Note dependencies (informational)

  • Parse Dependencies section from proposal
  • For each dependency, check if it exists in archive/ (satisfied) or specs/.delta/ (not satisfied)
  • If unsatisfied dependencies exist:
    • Note to user: "Dependencies: <name> (not yet archived)"
    • Proceed without asking - planning is safe and doesn't require dependencies
  • Planning can always proceed; dependencies are enforced at /ds:tasks and /ds:archive

Step 4: Explore the codebase

  • Find relevant existing code and patterns
  • Identify frameworks and conventions in use
  • Determine which files will likely need changes
  • Understand the current architecture

Step 5: Update proposal if needed

During exploration, if you discover:

  • The scope needs adjustment
  • Something should be added to "Out of Scope"
  • New capabilities are needed
  • The problem statement needs refinement

→ Update proposal.md and note the changes to the user.

Step 6: Create/update design.md

See design-template.md for the design document format. Fill in each section based on codebase exploration findings.

Step 7: Create delta specs

  • Determine which spec domains are affected
  • Create delta specs in specs/.delta/<name>/specs/<domain>.md
  • Use the delta format (ADDED/MODIFIED/REMOVED sections)
  • If main spec doesn't exist yet, note it will be created

Delta Format

See delta-format.md for the delta spec format.

Download now (ZIP)

  • Other versions181 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 181

    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

    171 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 repository12 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.

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