execute-plan skillA
execute-plan is agent-read markdown (skill) from teambrilliant/dev-skills: Execute an approved plan from thoughts/plans/ to completion — every phase, every check, every acceptance criterion — and stop only when DONE or BLOCKED. Use when someone says "execute the plan", "implement the plan", "build it" after a plan was approved, "start building", or points at a file in thoughts/plans/. Medium/large work without a plan → /dev-skills:write-plan first..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
# Execute Plan Carry an approved plan through to working, verified code. The plan is a contract: you either satisfy it or show exactly why it can't be satisfied. ## Input A plan in `thoughts/plans/` (from `/dev-skills:write-plan`). No plan and the work is medium/large → write one first. No plan and the work is small and clear → state the acceptance criteria in one line each, then run under the same contract. ## The Contract Approval of the plan is the only gate. From then on you own delivering it, and a run ends in exactly one of two states: **DONE** — every phase implemented; every phase check green; full test suite, typecheck and lint with no new failures against the baseline you recorded at the start; every acceptance criterion verified with cited evidence. For UI criteria, that means you ran `/dev-skills:qa-test` yourself and it passed. **BLOCKED** — the contract can't be satisfied without something only the user can provide: - a permission, credential, or access you don't have (and the plan's pre-flight blockers didn't cover) - a harness that can't be made runnable by you — a check needs a human step with no bypass …
Read the whole file at its exact version.
How to install
mdr add teambrilliant/dev-skills/execute-plan@git:20260927.b9558d0mdr add teambrilliant/dev-skills/execute-plan@sha256:8464b808186ebc9cPin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
[](https://markdownregistry.com/a/art_k6vhpkvybltthmqd)
0 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7394 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
teambrilliant/dev-skills · 6 stars · license none · pushed 2026-09-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_k6vhpkvybltthmqd GET https://markdownregistry.com/api/v1/resolve?ref=teambrilliant/dev-skills/execute-plan GET https://markdownregistry.com/api/v1/blob/8464b808186ebc9c8cb4932214d519d80c439969bbe8a12dd8b09cee474f5ff2
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from teambrilliant/dev-skills
Every file in teambrilliant/dev-skills