create-skill
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing…
@antinomyhqInstall SkillDevelopment
Skill
/execute-plan
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.
Claude Code
$ npx -y skills add tailcallhq/forgecode --skill execute-plan --agent claude-code
Codex
$ npx skills add tailcallhq/forgecode --skill execute-plan -a codex -y
Cursor
$ npx skills add tailcallhq/forgecode --skill execute-plan -a cursor -y
Gemini CLI
$ npx skills add tailcallhq/forgecode --skill execute-plan -a gemini-cli -y
GitHub Copilot
$ npx skills add tailcallhq/forgecode --skill execute-plan -a github-copilot -y
OpenCode
$ npx skills add tailcallhq/forgecode --skill execute-plan -a opencode -y
Windsurf
$ npx skills add tailcallhq/forgecode --skill execute-plan -a windsurf -y
SKILL.md
execute-plan.SKILL.mdname: 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
1. User provides: "Execute plan at plans/2025-11-23-refactor-auth-v1.md" 2. Recite commitment: "I will execute this plan to completion..." 3. Read the plan file 4. Find first `[ ]` (PENDING) task 5. Update to `[~]` (IN_PROGRESS) 6. Execute the task 7. Update to `[x]` (DONE) 8. Move to next PENDING task 9. Repeat until all tasks appear DONE 10. Re-read plan file to verify completion 11. Announce completion
Read more
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
1. User provides: "Execute plan at plans/2025-11-23-refactor-auth-v1.md" 2. Recite commitment: "I will execute this plan to completion..." 3. Read the plan file 4. Find first `[ ]` (PENDING) task 5. Update to `[~]` (IN_PROGRESS) 6. Execute the task 7. Update to `[x]` (DONE) 8. Move to next PENDING task 9. Repeat until all tasks appear DONE 10. Re-read plan file to verify completion 11. Announce completion
Ships withforgecode
AI enabled pair programmer for Claude, GPT, O Series, Grok, Deepseek, Gemini and 300+ models
7.6k3 skills3 agents
Stars on GitHub
Momentum
- stars in total
- 7.6k
Other skills on forgecode.
@antinomyhqInstall Skillgithub-pr-description
Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a…
@antinomyhqInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about execute-plan.
- Which coding agents can use execute-plan?
- execute-plan installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.