Skip to content
Skills Library
Programming · Automation

execute-plan

/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.

Repository
forge ↗
Licence
Apache-2.0
Last repository change
31.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 31.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

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.

Original author 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.

How it works

  1. Commitment to Completion
  2. Execution Steps
  3. Task Status Format
  4. Example Usage
Original SKILL.md headings · 50 lines, 241 words
SKILL.md preview
---
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

Versions

RepositoryScoreLicence
This page · antinomyhq/forge100Apache-2.0
nigelng/nng-kit100MIT
jelvodev/yaap100MIT
pinkroosterai/PinkRoosterSkills100MIT
zhixuan312/multi-model-agent100MIT
wezzard/amplify100MIT
Ovich/charrette90MIT
Uniswap/ai-toolkit84MIT

Database snapshot: 13.11.2026 · package version 22c4261bcdc2 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100execute
    Execute an approved implementation plan from .ai/plans/ task by task, running each task's verification and committing per task via the check-and-commit gate. Use when asked to "execute the plan", "implement the plan", or after /plan approval. Do not use without an approved plan…
  • 100executing-plans
    Use when you have an implementation plan ready to execute. Triggers: 'run the plan', 'start building', 'execute the tasks', 'implement the steps', 'next task in the plan', 'work through the plan'. Also invoked by develop after planning phase completes. NOT for: creating plans (use writing-plans).
  • 100executing-plans
    Execute a written implementation plan with review checkpoints and structured progress tracking. Use when you have a spec or plan ready to implement, when user says "execute this plan", "implement this spec", "carry out these steps", or "start working on the plan".
  • 92plan-execute
    Execute the user's plan that has been iteratively refined, step by step, with resume on failure. Use when the user runs /plan-execute or asks to execute an existing plan.
  • 100execute
    Dispatch and execute implementation plans with TDD and checkpoints. Use when plan is ready. Parallel by default for independent tasks.
  • 90execute
    作成済みの docs/plans/task-*.md を、永続的な進捗・証拠・判断ログを更新しながら自律的に実行する。計画の実装、再開、完了に /dev-core:execute を使う。親が実装し、委譲とレビューは条件に該当するときだけ行う。commit・push・PR は明示指定時だけ行う。

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.