execute-plan skillA
execute-plan is agent-read markdown (skill) from tailcallhq/forgecode: Execute structured task plans with status tracking. Use when the user provides a plan file path in the format `plans/{current-date}-{task-name}-{version}.md` or explicitly asks you to execute a plan file..
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 Execute structured task plans with automatic status tracking and progress updates. ## Commitment to Completion When a plan is provided, **all tasks in the plan must be completed**. Before starting execution, recite: > "I will execute this plan to completion. All the 20 tasks will be addressed and marked as DONE." ## Execution Steps **STEP 1**: Recite the commitment to complete all tasks in the plan. **STEP 2**: Read the entire plan file to identify pending tasks based on `task_status`. **STEP 3**: Announce the next pending task and update its status to `IN_PROGRESS` in the plan file. **STEP 4**: Execute all actions required to complete the task and mark the task status to `DONE` in the plan file. **STEP 5**: Repeat from Step 3 until all tasks are marked as `DONE`. **STEP 6**: Re-read the plan file to verify all tasks are completed before announcing completion. ## Task Status Format Use these status indicators in the plan file: ``` [ ]: PENDING [~]: IN_PROGRESS [x]: DONE [!]: FAILED ``` ## Example Usage 1. User provides: "Execute plan at plans/2025-11-23-refactor-auth-v1.md" 2. Recite commitment: "I will execute this plan to completion..." …
Read the whole file at its exact version.
How to install
mdr add tailcallhq/forgecode/execute-plan@git:20251124.2b8f212mdr add tailcallhq/forgecode/execute-plan@sha256:9c8829abd2967236Pin 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_glyzfnlpsnnmioi5)
2 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 (1704 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
tailcallhq/forgecode · 7,637 stars · license Apache-2.0 · pushed 2026-09-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_glyzfnlpsnnmioi5 GET https://markdownregistry.com/api/v1/resolve?ref=tailcallhq/forgecode/execute-plan GET https://markdownregistry.com/api/v1/blob/9c8829abd29672367a734197043d3741c6bae7da270ca15f5c045e47a4925318
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 tailcallhq/forgecode
Every file in tailcallhq/forgecode