executing-plans SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 3 indexed copies. Same content hash, so the same checks give both the same grade.
executing-plans from ddtcorex/maestro-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ddtcorex/maestro-skills/executing-plans@git:20261021.e9d05f9Pins git:20261021.e9d05f9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ddtcorex/maestro-skills
- Path
skills/executing-plans/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261021.e9d05f9, committed Oct 21, 2026
- First version recorded
- Aug 22, 2026
- Size
- 18,103 bytes
- Repository stars
- 5
- License
- MIT
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Executing Plans Execute the plan yourself, task by task, in this session: no implementer subagent per task, no reviewer per task. One fresh-context review of the whole branch at the end. **Why inline:** Subagent-driven development pays for a fresh implementer and a fresh reviewer on every task, each re-reading the codebase from zero. Inline execution pays for one context (yours) plus one reviewer at the end. What it gives up is a fresh context per task and a second pair of eyes per task. This skill keeps what those two things bought, by other means: the brief is the spec, the ledger is your memory, TDD is the per-task gate, and the final reviewer is the second pair of eyes. **Core principle:** The plan already did the thinking. Execute it exactly, prove each step with a test you watched fail and then pass, and leave a record that survives your own forgetting. **Narration:** between tool calls, narrate at most one short line — the ledger and the tool results carry the record. **Continuous execution:** Do not pause to check in with your human partner between tasks. They chose inline execution to spend less, not to answer …
Read the whole file at its exact version.
How to install
mdr add ddtcorex/maestro-skills/executing-plans@sha256:e4649e59880ef264The line at the top of this page pins the label git:20261021.e9d05f9, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_jgasc7acb4be7quz)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 22, 2026 and Oct 21, 2026, about one every 30 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261021.e9d05f9 latest | 2026-10-21 | e9d05f9 | 18,103 B | A | view · diff |
| git:20260919.2c4bbac | 2026-09-19 | 2c4bbac | 20,405 B | A | view · diff |
| git:20260822.9d40859 | 2026-08-22 | 9d40859 | 2,305 B | A | view |
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 (18103 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
ddtcorex/maestro-skills · 5 stars · license MIT · pushed 2026-10-27 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_jgasc7acb4be7quz GET https://markdownregistry.com/api/v1/resolve?ref=ddtcorex/maestro-skills/executing-plans GET https://markdownregistry.com/api/v1/blob/e4649e59880ef2643d1da128e3d607e87e3f969410d72095a5bf65811b6036dc
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from ddtcorex/maestro-skills
Every file in ddtcorex/maestro-skills