agentleFS
Sign inStart free
rakaarwakyrakaarwaky/agents-arwaky/skills/software-development/execute-plan/SKILL.md

execute-plan

Skill0 starsChanged 3 days agoMITView on GitHub

Executes a PR Plan DAG end-to-end: Hermes validates the plan and drops /execute-plan into Grok Build (Grok runs parallel Orca worktrees, implementers, the 3-reviewer panel, fix loops, and final assembly), then Hermes verifies the final branch and ships the PR.

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

  • MicrosoftSkill

    grill-with-docs

    Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

    Also in 4 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

  • +1 more from google

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read only the winning lane's references.

    line 30

“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 Skill

You orchestrate a PR Plan DAG end-to-end. This file is the lane identification step only; the working method lives in references/hermes/ and references/grok/.

Global Rules

The lane is determined from a physical signal, not by self-identification. Each agent's launcher stamps a fixed attribution env var into every command it runs; the model cannot set these.

if [[ -n "${HERMES_AGENT:-}" ]]; then echo HERMES
elif [[ -n "${GROK_AGENT:-}" ]]; then echo GROK
else echo UNSET; fi
  • HERMES → Hermes lane. Read references/hermes/. Stop.
  • GROK → Grok lane. Read references/grok/. Stop.
  • UNSET → stop and report. Do not guess the lane.

Marker provenance:

  • Hermes re-exports AI_AGENT=hermes-agent and HERMES_AGENT=true on every command.
  • Grok Build runs with GROK_AGENT=1.

Read only the winning lane's references. Do not read the other lane's.

Routing

Hermes lane (Steps 0–3)

StepReferencePurpose
0references/hermes/step-0-plan-and-spawn.mdValidate the DAG with validate-plan.py; plan the brief; create the Orca worktree with --agent grok; drop /execute-plan <design-doc-path>
1references/hermes/step-1-wait-grok.mdWait for Grok to finish the full execution loop; read its state file and artifacts
2references/hermes/step-2-verify-and-ship.mdVerify Grok's final branch (on origin, local gate clean); handle partial failures; report
3references/hermes/step-3-final-report.mdFlush new issue patterns to the workspace memory file (if any); final report to the user

Grok lane (Steps 0–13, run by Grok Build)

StepReferencePurpose
0references/grok/step-0-setup.mdSetup, state, personas, Orca protocol, invocation
1references/grok/step-1-memory-retrieval.mdPast issues briefing
2references/grok/step-2-tool-detection.mdDetect Orca and gh
3references/grok/step-3-parse-dag.mdParse PR Plan DAG
4references/grok/step-4-dag-processing.mdSort and linearize DAG for merge order
5references/grok/step-5-branch-prep.mdPrepare local modular branches
6references/grok/step-6-execution-loop.mdRun parallel implementer subagents
7references/grok/step-7-review.mdRun per-PR reviewer panel and fix loop
8references/grok/step-8-failure-handling.mdHandle failed or skipped PRs
9references/grok/step-9-resumption.mdResume previous run
10references/grok/step-10-stack-assembly.mdFinal branch assembly, final review, push 1 PR
11references/grok/step-11-cleanup.mdCleanup worktrees and artifacts
12references/grok/step-12-memory-flush.mdFlush memory
13references/grok/step-13-final-report.mdFinal report

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