agentleFS
Sign inStart free
marylinmarylin/Continuum/skills/plan/SKILL.md

plan

Skill0 starsChanged 7 months agoMITView on GitHub

Create a structured implementation plan with sized tasks and acceptance criteria. Use when starting any non-trivial feature (3+ steps), when a task feels ambiguous, or when you need to break down a large request before coding.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 3

    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:

    Check .lifecycle/lessons/ for lessons on relevant topics.

    line 13
  2. Distinctive:

    Write detailed specs upfront to reduce ambiguity during execution

    line 41
  3. Very specific:

    Update progress as tasks complete: [ ] → [x]

    line 58
  4. Distinctive:

    Do NOT ask between tasks — execute to completion

    line 59
  5. Very specific:

    If context limit approaching: run /checkpoint, commit, /compact, resume with /resume

    line 60
  6. Distinctive:

    If something goes sideways mid-execution: STOP and re-plan

    line 61

“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

Create Plan

Analyze this request and create a structured implementation plan.

Before planning

Check .lifecycle/lessons/ for lessons on relevant topics. Also check docs/06-Development/lessons.md as v1.x fallback. Skip if neither exists.

Create plan file

Write .lifecycle/plans/[name]-plan.md:

# [Feature Name] Plan

## Summary
[2-3 sentences. What and why.]

## Tasks
1. [S] Task — acceptance criteria in one line
2. [M] Task — criteria
3. [L] Task — criteria

## Dependencies
[Only if tasks depend on each other. Skip if none.]

## Open Questions
[Anything ambiguous. Skip if clear.]

Rules:

  • One line per task. No paragraphs, no prose.
  • Complexity: S = <30min, M = 1-3hrs, L = 3hrs+
  • Reference external docs instead of inlining
  • Write detailed specs upfront to reduce ambiguity during execution

Present and wait

Show summary and any open questions. Do NOT start coding until approved.

On approval

  1. Create .lifecycle/plans/[name]-progress.md:
    # [Feature Name] Progress

[ ] Task 1
[ ] Task 2
[ ] Task 3
  2. Begin executing the first task immediately (same session)
  3. Update progress as tasks complete: [ ] → [x]
  4. Do NOT ask between tasks — execute to completion
  5. If context limit approaching: run /checkpoint, commit, /compact, resume with /resume
  6. If something goes sideways mid-execution: STOP and re-plan

Request: $ARGUMENTS

Download now (ZIP)

  • Other versions184 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 184

    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. kdlbs/kandev★ 1ksame name
    7. suboss87/FDEOps★ 940same name
    8. loongclaw-ai/loongclaw★ 640same name
    9. witnesstodark/mr-mak-workspace★ 609same name
    10. Tommy-yw/RunbookHermes★ 546same name

    174 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

    • 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

    • gaebalaiSkill

      design-tracker

      PROACTIVELY track and document project design decisions without being asked. Activate automatically when detecting architecture discussions, implementation decisions, pattern choices, library selections, or any technical decisions. Also use when user explicitly says "記録して", "設計どうなってる", "record this". Do NOT wait for user to ask - record important decisions immediately.

      Also in 3 projects that use this

    • +3 more from math-inc
    • +2 more from gaebalai
  • In this repository6 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