agentleFS
Sign inStart free
gerard-labsgerard-labs/superpowers-api-platform/skills/executing-plans/SKILL.md

executing-plans

Skill2 starsChanged 6 months agoMITView on GitHub

Execute a hors-pipeline implementation plan with checkpoints, TDD discipline, and continuous validation. Each plan step has explicit AC + validation commands; you run them, capture output, and proceed only on green. NOT used inside `/api-resource-pipeline` — the pipeline has its own dev/test/review stages. Use for manual execution of `gerard:writing-plans` outputs.

189 other projects use a version of this.

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

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

  • 0

    Common

    Most of the 178 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the plan (from gerard:writing-plans or a markdown plan file).

    line 24
  2. Distinctive:

    Run the validation commands.

    line 28
  3. Very specific:

    After the last step : full quality gate (/symfony-check or equivalent).

    line 31
  4. Distinctive:

    No silent trim of plan steps — if a step doesn't make sense anymore, document why and update the plan.

    line 36

“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 (hors pipeline)

Use when

  • Executing a plan produced by gerard:writing-plans (or any hors-pipeline plan)
  • Stepping through a multi-skill refactor with checkpoints
  • Manual TDD on a non-API-Platform feature
  • Migration that needs checkpointed validation between steps

Not for: API Platform features in pipeline mode. Use /api-resource-pipeline or /api-resource-ship — those have their own dev/test/review stages with state files and REQUEST_CHANGES loop.

Default workflow

  1. Read the plan (from gerard:writing-plans or a markdown plan file).
  2. For each step :
    • Re-read the step's AC + dependencies + validation commands.
    • Implement minimally to satisfy the AC.
    • Run the validation commands.
    • On red: fix in-session, re-run.
    • On green: checkpoint, move to next step.
  3. After the last step : full quality gate (/symfony-check or equivalent).
  4. Summarize what was shipped + follow-up backlog.

Guardrails

  • One step at a time. No batching that breaks the checkpoint discipline.
  • No silent trim of plan steps — if a step doesn't make sense anymore, document why and update the plan.
  • TDD when applicable: RED → GREEN → REFACTOR per step.
  • For API Platform: redirect to the pipeline commands.

Progressive disclosure

  • This file for execution posture
  • reference.md for deeper patterns
  • docs/complexity-tiers.md for sizing

Output contract

  • Per-step execution trace (AC met / validation green / files touched)
  • Final summary + follow-ups

References

  • reference.md
  • docs/complexity-tiers.md
  • docs/symfony/pipeline-overview.md — for the API Platform pipeline alternative

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