execute-plan
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.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- execute-plan
- description
- 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.
- when-to-use
- Use for /execute-plan <design-doc-path>, execute plan, run the plan, implement the design, or after /design produces a PR plan.
- argument-hint
- <design-doc-path> [--resume <PLAN_ID>]
02 资源文件 20
- 参考文档references/grok/step-0-setup.md6.8 KB
- 参考文档references/grok/step-1-memory-retrieval.md2.3 KB
- 参考文档references/grok/step-10-stack-assembly.md7.1 KB
- 参考文档references/grok/step-11-cleanup.md1.8 KB
- 参考文档references/grok/step-12-memory-flush.md5.4 KB
- 参考文档references/grok/step-13-final-report.md1.2 KB
- 参考文档references/grok/step-2-tool-detection.md713 B
- 参考文档references/grok/step-3-parse-dag.md5.1 KB
- 参考文档references/grok/step-4-dag-processing.md2.0 KB
- 参考文档references/grok/step-5-branch-prep.md2.2 KB
- 参考文档references/grok/step-6-execution-loop.md3.7 KB
- 参考文档references/grok/step-7-review.md10.4 KB
- 参考文档references/grok/step-8-failure-handling.md1.2 KB
- 参考文档references/grok/step-9-resumption.md4.0 KB
- 参考文档references/hermes/step-0-plan-and-spawn.md3.6 KB
- 参考文档references/hermes/step-1-wait-grok.md1.5 KB
- 参考文档references/hermes/step-2-verify-and-ship.md2.0 KB
- 参考文档references/hermes/step-3-final-report.md1.5 KB
- 脚本scripts/host.py2.4 KB
- 脚本scripts/validate-plan.py11.0 KB
03 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. Readreferences/hermes/. Stop.GROK→ Grok lane. Readreferences/grok/. Stop.UNSET→ stop and report. Do not guess the lane.
Marker provenance:
- Hermes re-exports
AI_AGENT=hermes-agentandHERMES_AGENT=trueon 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)
| Step | Reference | Purpose |
|---|---|---|
| 0 | references/hermes/step-0-plan-and-spawn.md |
Validate the DAG with validate-plan.py; plan the brief; create the Orca worktree with --agent grok; drop /execute-plan <design-doc-path> |
| 1 | references/hermes/step-1-wait-grok.md |
Wait for Grok to finish the full execution loop; read its state file and artifacts |
| 2 | references/hermes/step-2-verify-and-ship.md |
Verify Grok's final branch (on origin, local gate clean); handle partial failures; report |
| 3 | references/hermes/step-3-final-report.md |
Flush new issue patterns to the workspace memory file (if any); final report to the user |
Grok lane (Steps 0–13, run by Grok Build)
04 同仓库更多 Skills
github-workflow
Umbrella for GitHub auth, repo management, issues, PRs, Mergify, and releases. Subsumes github-auth and repo-manager.
brave-automation
baa CLI: Brave profiles, Google sessions, credentials.
aes
AES docs, layers, rule fixes, and legacy migration.
pretext
Build creative browser demos with DOM-free text layout.
popular-web-designs
54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.
p5js
p5.js sketches: gen art, shaders, interactive, 3D.