agentleFS
Sign inStart free
RBraga01RBraga01/a-team/skills/executing-plans/SKILL.md

executing-plans

Skill24 starsChanged 24 days agoMITView on GitHub

Use when you have a written implementation plan to execute in the current session. Loads the plan, reviews critically, executes all tasks, and reports when complete.

189 other projects use a version of this, 113 of them edited.

Adopted by

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. 5 are common, 5 are distinctive, and 1 is very specific to this project.

  • 5

    Common

    Most of the 178 edited versions we read keep these.

  • 5

    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:

    Prefer subagent-driven-development over this skill: when subagents are available — it provides higher quality through per-task fresh …

    line 12
  2. Distinctive:

    Read plan file completely

    line 18
  3. Common:

    If concerns: raise with human partner BEFORE starting

    line 20
  4. Distinctive:

    If no concerns: create TodoWrite and proceed

    line 21
  5. Common:

    Follow each step exactly (plan has bite-sized steps)

    line 27
  6. Common:

    Run verifications as specified

    line 28
  7. Common:

    After all tasks complete:

    line 35
  8. Distinctive:

    Verify tests, update docs, commit

    line 37
  9. Distinctive:

    Never start on main/master branch without explicit user consent

    line 50
  10. Distinctive:

    Follow plan steps exactly — don't improvise

    line 51
  11. Common:

    Stop when blocked, don't guess

    line 52

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

Executing Plans

Load plan, review critically, execute all tasks, report when complete.

Announce at start: "I'm using the executing-plans skill to implement this plan."

Prefer subagent-driven-development over this skill when subagents are available — it provides higher quality through per-task fresh context and two-stage review.

The Process

Step 1: Load and Review Plan

  1. Read plan file completely
  2. Review critically — identify questions or concerns about the plan
  3. If concerns: raise with human partner BEFORE starting
  4. If no concerns: create TodoWrite and proceed

Step 2: Execute Tasks

For each task:

  1. Mark as in_progress
  2. Follow each step exactly (plan has bite-sized steps)
  3. Run verifications as specified
  4. Mark as completed

Do not pause to check in between tasks unless blocked.

Step 3: Complete Development

After all tasks complete:

  • Use finishing-a-development-branch skill
  • Verify tests, update docs, commit

When to Stop and Ask

STOP executing immediately when:

  • Hit a blocker (missing dependency, test fails, instruction unclear)
  • Plan has critical gaps preventing starting
  • Verification fails repeatedly

Ask for clarification rather than guessing.

Hard Rules

  • Never start on main/master branch without explicit user consent
  • Follow plan steps exactly — don't improvise
  • Stop when blocked, don't guess
  • Skip nothing in the verification steps

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