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.

153 stars

Best use case

execute-plan is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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.

Teams using execute-plan should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/execute-plan/SKILL.md --create-dirs "https://raw.githubusercontent.com/Microck/ordinary-claude-skills/main/skills_all/execute-plan/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/execute-plan/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How execute-plan Compares

Feature / Agentexecute-planStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

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.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# 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

Related Skills

writing-plans

153
from Microck/ordinary-claude-skills

Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge

treatment-plans

153
from Microck/ordinary-claude-skills

Generate concise (3-4 page), focused medical treatment plans in LaTeX/PDF format for all clinical specialties. Supports general medical treatment, rehabilitation therapy, mental health care, chronic disease management, perioperative care, and pain management. Includes SMART goal frameworks, evidence-based interventions with minimal text citations, regulatory compliance (HIPAA), and professional formatting. Prioritizes brevity and clinical actionability.

story-explanation

153
from Microck/ordinary-claude-skills

Create compelling story-format summaries using UltraThink to find the best narrative framing. Support multiple formats - 3-part narrative, n-length with inline links, abridged 5-line, or comprehensive via Foundry MCP. USE WHEN user says 'create story explanation', 'narrative summary', 'explain as a story', or wants content in Daniel's conversational first-person voice.

sales-comp-plan-designer

153
from Microck/ordinary-claude-skills

Base/variable split recommendations, accelerators, decelerators, quota retirement methods, SPIFs, cost of sales tracking.

project-planning

153
from Microck/ordinary-claude-skills

Generate structured planning documentation for web projects with context-safe phases, verification criteria, and exit conditions. Creates IMPLEMENTATION_PHASES.md plus conditional docs (DATABASE_SCHEMA, API_ENDPOINTS, UI_COMPONENTS, CRITICAL_WORKFLOWS). Use when: starting new Cloudflare Workers/React projects, adding major features to existing apps, breaking large work into manageable phases, or need verified planning before coding begins.

create-plans

153
from Microck/ordinary-claude-skills

Create hierarchical project plans optimized for solo agentic development. Use when planning projects, phases, or tasks that Claude will execute. Produces Claude-executable plans with verification criteria, not enterprise documentation. Handles briefs, roadmaps, phase plans, and context handoffs.

create-plan

153
from Microck/ordinary-claude-skills

Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. All plans MUST be validated using the included validation script. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.

zapier-workflows

153
from Microck/ordinary-claude-skills

Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.

writing-skills

153
from Microck/ordinary-claude-skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dependencies, and rust-documentation skills.

workflow-orchestration-patterns

153
from Microck/ordinary-claude-skills

Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.

workflow-management

153
from Microck/ordinary-claude-skills

Create, debug, or modify QStash workflows for data updates and social media posting in the API service. Use when adding new automated jobs, fixing workflow errors, or updating scheduling logic.

workflow-interactive-dev

153
from Microck/ordinary-claude-skills

用于开发 FastGPT 工作流中的交互响应。详细说明了交互节点的架构、开发流程和需要修改的文件。