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

executing-plans

Skill1 starsChanged 9 months agoNo licenceView on GitHub

Use when you have a written implementation plan to execute in a separate session with review checkpoints

192 other projects use a version of this, 102 of them edited; 92 of 105 edited versions we compared changed its rules; 4 new projects in the last 4 weeks, against 5 the 4 before.

How people change it

92 of 105 edited versions changed its rules, and some changes recur.

Of the 105 edited versions we compared: 11 keep every rule, 2 are an older text, 92 made changes of their own.

Not in older versions

  1. REQUIRED SUB-SKILL: Use superpowers:finishing-a-development-branchmissing from 2 of 2

Rules people drop

  1. If no concerns: Create TodoWrite and proceeddropped by 38 of 92
  2. REQUIRED SUB-SKILL: Use superpowers:finishing-a-development-branchdropped by 17 of 92
  3. Follow that skill to verify tests, present options, execute choicedropped by 12 of 92
  4. Don't force through blockers - stop and ask.dropped by 7 of 92
  5. If concerns: Raise them with your human partner before startingdropped by 6 of 92
  6. Stop when blocked, don't guessdropped by 5 of 92
  7. Run verifications as specifieddropped by 5 of 92
  8. Follow plan steps exactlydropped by 4 of 92

Rules people add

  1. A rule we can't quote: its licence doesn't allow itadded by 82 of 92
  2. A rule we can't quote: its licence doesn't allow itadded by 29 of 92
  3. A rule we can't quote: its licence doesn't allow itadded by 18 of 92
  4. REQUIRED SUB-SKILL: Use /skill:finishing-a-development-branchadded by 3 of 92
  5. A rule we can't quote: its licence doesn't allow itadded by 2 of 92
  6. A rule we can't quote: its licence doesn't allow itadded by 2 of 92
  7. A rule we can't quote: its licence doesn't allow itadded by 2 of 92
  8. A rule we can't quote: its licence doesn't allow itadded by 2 of 92

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: 4 new projects took it in the last 4 weeks, 0.8× the 4 weeks before.thin data

Week of Sep 20: 1 new projectWeek of Sep 27: 0 new projectsWeek of Oct 4: 2 new projectsWeek of Oct 11: 2 new projectsWeek of Oct 18: 1 new projectWeek of Oct 25: 1 new projectWeek of Nov 1: 2 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 9 in all, so this is a hint, not a trend.

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

  • obraSkill

    diagnosing-superpowers

    Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

    Also in 20 projects that use this

  • allanninalSkill

    algorand-vulnerability-scanner

    Scans Algorand smart contracts for 11 common vulnerabilities including rekeying attacks, unchecked transaction fees, missing field validations, and access control issues. Use when auditing Algorand projects (TEAL/PyTeal). (project, gitignored)

    Also in 4 projects that use this

  • allanninalSkill

    cairo-vulnerability-scanner

    Scans Cairo/StarkNet smart contracts for 6 critical vulnerabilities including felt252 arithmetic overflow, L1-L2 messaging issues, address conversion problems, and signature replay. Use when auditing StarkNet projects. (project, gitignored)

    Also in 4 projects that use this

  • farslabSkill

    aws-agentic-ai

    AWS Bedrock AgentCore comprehensive expert for deploying and managing AI agents at scale. Use when working with any AgentCore service including Gateway, Runtime, Memory, Identity, Code Interpreter, Browser, Observability, Agent Registry, or Evaluations. Covers agent deployment, MCP tool integration, credential management, agent discovery, governance workflows, and automated quality assessment. Essential when user mentions AgentCore, agent runtime, agent registry, agent evaluation, MCP gateway, deploy agent, register MCP server, discover agents, evaluate agent quality, agent credentials, or wants to build, deploy, catalog, or monitor AI agents on AWS.

    Also in 3 projects that use this

  • +3 more from Leodorareluctant259
  • +1 more from allanninal

The file

We split this skill into the rules it gives an agent

11 rules. 4 are common, 7 are distinctive, and 0 are very specific to this project.

  • 4

    Common

    Most of the 164 edited versions we read keep these.

  • 7

    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 164 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.