Agent skill

Execute Plan With Status Tracking

Works through a plan file task by task, updating each task's status inside the file, then re-reads it at the end to confirm nothing was left undone.

Apache-2.0Auto-check passedAgent Workflows

Install Execute Plan With Status Tracking

skills CLI

$ npx skills add tailcallhq/forgecode --skill execute-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install tailcallhq/forgecode execute-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/crates/forge_repo/src/skills/execute-plan .claude/skills/execute-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "execute-plan" agent skill from https://github.com/tailcallhq/forgecode/tree/main/crates/forge_repo/src/skills/execute-plan into .claude/skills/execute-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute-plan", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/tailcallhq/forgecode/tree/main/crates/forge_repo/src/skills/execute-plan

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add tailcallhq/forgecode --skill execute-plan -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install tailcallhq/forgecode execute-plan --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .agents/skills && cp -r skills-src/crates/forge_repo/src/skills/execute-plan .agents/skills/execute-plan && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "execute-plan" agent skill from https://github.com/tailcallhq/forgecode/tree/main/crates/forge_repo/src/skills/execute-plan into .agents/skills/execute-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute-plan", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add tailcallhq/forgecode --skill execute-plan -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install tailcallhq/forgecode execute-plan --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/crates/forge_repo/src/skills/execute-plan .cursor/skills/execute-plan && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "execute-plan" agent skill from https://github.com/tailcallhq/forgecode/tree/main/crates/forge_repo/src/skills/execute-plan into .cursor/skills/execute-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute-plan", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/tailcallhq/forgecode.git --path crates/forge_repo/src/skills/execute-plan

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add tailcallhq/forgecode --skill execute-plan -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install tailcallhq/forgecode execute-plan --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/crates/forge_repo/src/skills/execute-plan .gemini/skills/execute-plan && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "execute-plan" agent skill from https://github.com/tailcallhq/forgecode/tree/main/crates/forge_repo/src/skills/execute-plan into .gemini/skills/execute-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute-plan", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install tailcallhq/forgecode execute-plan

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add tailcallhq/forgecode --skill execute-plan -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .github/skills && cp -r skills-src/crates/forge_repo/src/skills/execute-plan .github/skills/execute-plan && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "execute-plan" agent skill from https://github.com/tailcallhq/forgecode/tree/main/crates/forge_repo/src/skills/execute-plan into .github/skills/execute-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute-plan", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add tailcallhq/forgecode --skill execute-plan -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install tailcallhq/forgecode execute-plan --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/crates/forge_repo/src/skills/execute-plan .opencode/skills/execute-plan && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "execute-plan" agent skill from https://github.com/tailcallhq/forgecode/tree/main/crates/forge_repo/src/skills/execute-plan into .opencode/skills/execute-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute-plan", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: execute-plan
GitHub stars: 7.6k
Used in: 1 other repo
Token cost: ~426 tokens
SKILL.md length: 221 words
Files: 1
Skills in repo: 14
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Works through a plan file task by task, updating each task's status inside the file, then re-reads it at the end to confirm nothing was left undone.

Works in 11 steps: User provides: "Execute plan at… → Recite commitment: "I will execute this… → Read the plan file → …
Running a written implementation plan from start to finish
SKILL.md covers Commitment to Completion, Execution Steps, Task Status Format and Example Usage
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

This skill makes the agent carry out a structured plan file, normally one with a path like plans/2025-11-23-refactor-auth-v1.md. Before it starts, the agent recites a commitment to finish every task in the plan. It then reads the whole file, finds the first pending task, announces it, marks it in progress, does the work and marks it done.

Status lives in the plan file itself, using checkbox-style markers for pending, in progress and done. The loop repeats until no pending tasks remain, and the file is read one more time to verify that every task is complete before the agent announces completion. It needs only the plan file and ships no scripts.

When your agent uses it

Running a written implementation plan from start to finish
Resuming a plan file in which some tasks are already marked done
Keeping a visible progress record inside the plan while the agent works

Example prompts

“Execute the plan at plans/2025-11-23-refactor-auth-v1.md and keep the task statuses updated.”
“Run the plan file I just wrote to completion and check that every task is marked done.”

Requirements

A plan file with a status marker on each task

Workflow steps

11 steps, taken from the first numbered list in SKILL.md.

User provides: "Execute plan at plans/2025-11-23-refactor-auth-v1.md"
Recite commitment: "I will execute this plan to completion..."
Read the plan file
Find first [ ] (PENDING) task
Update to [~] (IN_PROGRESS)
Execute the task
Update to [x] (DONE)
Move to next PENDING task
Repeat until all tasks appear DONE
Re-read plan file to verify completion
Announce completion

What it can do on your machine

Read from SKILL.md and the folder at commit 92a5699. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Execute Plan With Status Tracking loads about 426 tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 221 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~54
When it runs · the whole SKILL.md, loaded when a task matches: ~426

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tailcallhq/forgecode at commit 92a5699, republished under its Apache-2.0 licence (© tailcallhq). 221 words, ~426 tokens.

Download SKILL.mdSave it as .claude/skills/execute-plan/SKILL.md (or your agent's skills folder).

name: execute-plan
description: 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.

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

User provides: "Execute plan at plans/2025-11-23-refactor-auth-v1.md"
Recite commitment: "I will execute this plan to completion..."
Read the plan file
Find first [ ] (PENDING) task
Update to [~] (IN_PROGRESS)
Execute the task
Update to [x] (DONE)
Move to next PENDING task
Repeat until all tasks appear DONE
Re-read plan file to verify completion
Announce completion

Files

Just SKILL.md in crates/forge_repo/src/skills/execute-plan of tailcallhq/forgecode.

Open the folder on GitHubat commit 92a5699

Used in 1 other repository

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in tailcallhq/forgecode, which our catalogue first saw on October 7, 2026.

Microck/ordinary-claude-skillsskills_all/execute-plan skills_categorized/health-fitness/execute-plan+1 more

Compare with similar skills

Execute Plan With Status Tracking next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Execute Plan With Status Tracking compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Execute Plan With Status Tracking this skilltailcallhq/forgecode	7.6k	1 repos	~426	Automated safety check: Pass	Apache-2.0	today
Inline Plan ExecutionjnMetaCode/superpowers-zh	8.3k	—	~2.5k	Automated safety check: Pass	MIT	3 days ago
Auditable Playbook Designercursor/plugins	10k	8 repos	~1k	Automated safety check: Pass	None	today
Iterative Development Orchestratorprime-radiant-inc/iterative-development	181	—	~2.7k	Automated safety check: Pass	Apache-2.0	4 mo ago
DeepSeek V4 Thinking-Mode Rulescodewhale-hq/Codewhale	41k	—	~443	Automated safety check: Pass	MIT	today
Fable Disciplineassafkip/kipi-system	112	—	~2.9k	Automated safety check: Pass	MIT	today

Similar skills

Inline Plan Execution
jnMetaCode/superpowers-zh
Executes a written implementation plan task by task in the current session, with a progress ledger, test-first gates and one fresh-context review at the end.
8.3k GitHub stars~2.5k tokensUpdated 3 days ago
Agent WorkflowsAuto-check passed
Auditable Playbook Designer
cursor/plugins
Official
Designs a step-by-step playbook for large or unfamiliar work, runs it as a loop of hypotheses and measurements, and logs decisions so a human can review them later.
10k GitHub starsUsed in 8 repos~1k tokens
Agent WorkflowsAuto-check passed
Iterative Development Orchestrator
prime-radiant-inc/iterative-development
Runs an autonomous loop that extracts requirements with proof obligations, builds a walking skeleton, then audits sprint by sprint against real behavior evidence.
181 GitHub stars~2.7k tokensUpdated 4 mo ago
Agent WorkflowsAuto-check passed
DeepSeek V4 Thinking-Mode Rules
codewhale-hq/Codewhale
Three rules for multi-step work with DeepSeek V4 thinking models: verify references, use a verifier subagent before big edits, and write plans with exact path and line.
41k GitHub stars~443 tokensUpdated today
Agent WorkflowsAuto-check passed
Fable Discipline
assafkip/kipi-system
Teaches staged, verifiable coding habits for multi-file tasks and ships a hook that blocks tests from touching live data.
112 GitHub stars~2.9k tokensUpdated today
Agent WorkflowsAuto-check passed
Goal Objective Drafter
QwenLM/qwen-code
Turns a vague intention into a /goal objective with one outcome, numbered yes-or-no checks, guardrails, a budget and a block protocol, without starting the work.
28k GitHub stars~3.5k tokensUpdated today
Agent WorkflowsAuto-check passed

More from tailcallhq/forgecode

All 14 skills in this repo

Git Merge Conflict Resolver
tailcallhq/forgecode
Resolves Git merge conflicts with a plan-first workflow that keeps both sides' intent, regenerates lock files and backs up deleted-but-modified files.
7.6k GitHub starsUsed in 1 repo~4.5k tokens
Auto-check passed
Forge CLI Debug Workflow
tailcallhq/forgecode
Gives a systematic process for debugging the forge CLI: build in debug mode, check the latest help output, test with the non-interactive -p flag, and clone conversations before reproducing bugs.
7.6k GitHub starsUsed in 1 repo~1.6k tokens
Auto-check passed
FIXME Resolver
tailcallhq/forgecode
Finds every FIXME comment in a codebase, groups related ones across files into one task, implements the work they describe and removes the comments once it is done.
7.6k GitHub stars~1.1k tokensUpdated today
Auto-check passed
Reasoning Serialization Tests
tailcallhq/forgecode
Checks that ReasoningConfig fields are serialized into the right provider-specific JSON for OpenRouter, Anthropic, GitHub Copilot and Codex requests.
7.6k GitHub stars~1k tokensUpdated today
Auto-check passed
Implementation Plan Creator
tailcallhq/forgecode
Writes a structured Markdown implementation plan with checkbox tasks, verification criteria and risks, then checks it with a validation script; no code changes.
7.6k GitHub starsUsed in 1 repo~1.1k tokens
Auto-check passed
Release Notes Writer
tailcallhq/forgecode
Pulls a GitHub release and every linked pull request, then writes polished, factual release notes from the combined set of changes.
7.6k GitHub stars~1.4k tokensUpdated today
Auto-check passed

Questions about Execute Plan With Status Tracking

What does Execute Plan With Status Tracking do?

Works through a plan file task by task, updating each task's status inside the file, then re-reads it at the end to confirm nothing was left undone. md. Before it starts, the agent recites a commitment to finish every task in the plan.

When should I use Execute Plan With Status Tracking?

Execute Plan With Status Tracking fits situations like: running a written implementation plan from start to finish; resuming a plan file in which some tasks are already marked done; keeping a visible progress record inside the plan while the agent works.

How do I install Execute Plan With Status Tracking in Claude Code?

Run `npx skills add tailcallhq/forgecode --skill execute-plan -a claude-code`. Or copy the skill folder (crates/forge_repo/src/skills/execute-plan in tailcallhq/forgecode) into .claude/skills/execute-plan in your project. Claude Code loads it when a task matches its description.

How do I install Execute Plan With Status Tracking in Codex?

Run `npx skills add tailcallhq/forgecode --skill execute-plan -a codex`. Or copy the skill folder (crates/forge_repo/src/skills/execute-plan in tailcallhq/forgecode) into .agents/skills/execute-plan in your project. Codex loads it when a task matches its description.

Can I use Execute Plan With Status Tracking in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tailcallhq/forgecode --skill execute-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/execute-plan, .gemini/skills/execute-plan, .github/skills/execute-plan and .opencode/skills/execute-plan in your project.

What does Execute Plan With Status Tracking need to run?

SKILL.md names no scripts, command-line tools or credentials: Execute Plan With Status Tracking is instructions for the agent only. Our summary lists: A plan file with a status marker on each task.

Does Execute Plan With Status Tracking access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Execute Plan With Status Tracking safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Execute Plan With Status Tracking use?

Execute Plan With Status Tracking is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Execute Plan With Status Tracking use?

About 426 tokens (SKILL.md is roughly 1.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Execute Plan With Status Tracking?

Skills that share tags, products or a category with Execute Plan With Status Tracking: Inline Plan Execution (jnMetaCode/superpowers-zh, 8.3k stars), Auditable Playbook Designer (cursor/plugins, 10k stars), Iterative Development Orchestrator (prime-radiant-inc/iterative-development, 181 stars) and DeepSeek V4 Thinking-Mode Rules (codewhale-hq/Codewhale, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Execute Plan With Status Tracking?

tailcallhq (a GitHub organization) maintains it in tailcallhq/forgecode, which has 7,642 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 7, 2026.

Source: tailcallhq/forgecode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Execute Plan With Status Tracking

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Execute Plan

Commitment to Completion

Execution Steps

Task Status Format

Example Usage

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from tailcallhq/forgecode

Related

Questions about Execute Plan With Status Tracking