agentleFS
AtilaMedeirosAtilaMedeiros/skills/writing-plans/SKILL.md

writing-plans

Skill1 starsChanged 9 months agoNo licenceView on GitHub

Use when you have a spec or requirements for a multi-step task, before touching code

198 other projects use a version of this, 128 of them edited; 100 of 119 edited versions we compared changed its rules; 11 new projects in the last 4 weeks, against 14 the 4 before.

How people change it

100 of 119 edited versions changed its rules, and some changes recur.

Of the 119 edited versions we compared: 19 keep every rule, 100 made changes of their own.

Rules people drop

  1. After saving the plan, offer execution choice:dropped by 42 of 100
  2. REQUIRED SUB-SKILL: Use superpowers:subagent-driven-developmentdropped by 31 of 100

Rules people add

  1. Before defining tasks, map out which files will be created or modified and what each one is responsible for. This is where decomposition decisions get locked in.added by 73 of 100
  2. If the spec covers multiple independent subsystems, it should have been broken into sub-project specs during brainstorming. If it wasn't, suggest breaking this into separate plans — one per subsystem. …added by 72 of 100
  3. 3. Type consistency: Do the types, method signatures, and property names you used in later tasks match what you defined in earlier tasks? A function called clearLayers() in Task 3 but clearFullLayers() in Task 7 is a bug.added by 64 of 100
  4. After writing the complete plan, look at the spec with fresh eyes and check the plan against it. This is a checklist you run yourself — not a subagent dispatch.added by 63 of 100
  5. If you find issues, fix them inline. No need to re-review — just fix and move on. If you find a spec requirement with no task, add the task.added by 62 of 100
  6. Context: If working in an isolated worktree, it should have been created via the superpowers:using-git-worktrees skill at execution time.added by 51 of 100
  7. A rule we can't quote: its licence doesn't allow itadded by 46 of 100
  8. A rule we can't quote: its licence doesn't allow itadded by 43 of 100

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Cooling: 11 new projects took it in the last 4 weeks, 0.8× the 4 weeks before.

Week of Sep 20: 3 new projectsWeek of Sep 27: 2 new projectsWeek of Oct 4: 5 new projectsWeek of Oct 11: 4 new projectsWeek of Oct 18: 2 new projectsWeek of Oct 25: 5 new projectsWeek of Nov 1: 3 new projectsWeek of Nov 8: 1 new project
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read.

Most recently taken up by

Used with

Projects with it also use chinese-code-review, chinese-commit-conventions 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.
  • Leodorareluctant259Skill

    chinese-code-review

    中文代码审查规范——在保持专业严谨的同时,用符合国内团队文化的方式给出有效反馈

    Also in 8 projects that use this

  • Leodorareluctant259Skill

    chinese-commit-conventions

    中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化

    Also in 8 projects that use this

  • ryanportfolioSkill

    addskill

    Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

    Also in 6 projects that use this

  • ryanportfolioSkill

    apply-firmware

    Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.

    Also in 6 projects that use this

  • +2 more from Leodorareluctant259
  • +6 more from ryanportfolio

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 156 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.