agentleFS
Sign inStart free
danielvm-gitdanielvm-git/bigpowers/skills/execute-plan/SKILL.md

execute-plan

Skill288 starsChanged 5 days agoMITView on GitHub

Batch-execute tasks from the active epic capsule sequentially, with a human checkpoint after each step. Use when user has an approved plan and wants step-by-step oversight.

25 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-plan, to-spec and 4 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.
  • JetBrainsSkill

    create-plan

    Research the codebase and create an implementation plan with architecture notes, design document, and track decomposition. Use when starting a new feature or large change.

    Also in 4 projects that use this

  • GoogleSkill

    to-spec

    Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 4 projects that use this

  • GoogleSkill

    domain-modeling

    Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

    Also in 3 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 3 projects that use this

  • +1 more from google

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 1

    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 specs/state.yaml (active_epic, active_story) and the matching specs/epics/*/epic.yaml.

    line 20
  2. Very specific:

    Update specs/execution-status.yaml when a story/epic completes (bash scripts/sync-status-from-epics.sh or direct edit).

    line 44
  3. Distinctive:

    Loop until behavioral correctness is verified: if a verify command passes but the observed behavior is still wrong, return to step 1 and …

    line 56

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

Execute Plan

Execute tasks from the active epic (specs/epics/eNN-slug/epic.yaml story tasks[]) one at a time, showing evidence after each step before proceeding.

HARD GATE — Do NOT proceed if on main or master. Run kickoff-branch first.

HARD GATE — Active epic must exist with runnable verify on each task. If missing, run plan-release then plan-work or build-epic.

Process

1. Read the plan

Read specs/state.yaml (active_epic, active_story) and the matching specs/epics/*/epic.yaml. Parse depends-on in task descriptions for execution waves.

CONTEXT ISOLATION — Spawn each skill with a fresh context window. Pass decisions only through specs/state.yaml handoff — never rely on prior chat history.

Confirm with the user: step count, skip/reorder, stop-after step.

2. Execute step by step

For each task in the active story:

a. Announce — task desc and verify command.

b. Execute — code or delegate-task / dispatch-agents for waves.

c. Run verify — must be green before advancing.

d. Log — non-obvious decisions in specs/state.yaml under decisions[] or handoff block.

e. Checkpoint — ask to proceed unless autonomous mode requested.

f. Story UAT — after last task, run manual verification script from story notes or verify-work.

On verify failure: fix and re-run; never advance on red.

Update specs/execution-status.yaml when a story/epic completes (bash scripts/sync-status-from-epics.sh or direct edit).

3. Blockers

Report blocker; ask skip/adapt/stop; update epic capsule if plan changes.

4. Final report

Suggest: verify-work → run-evals → audit-code → simulate-agents → commit-message → release-branch

Rules

  • Loop until behavioral correctness is verified: if a verify command passes but the observed behavior is still wrong, return to step 1 and run the execution cycle again.
<!-- story: e02s03 --><!-- story: e05s02 --><!-- story: e08s01 -->

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.

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