execute-plan

Execute verified implementation plan tasks in deterministic 5-task batches.

1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/n0rvyn/indie-toolkit --skill execute-plan-n0rvyn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execute-plan
Source: https://github.com/n0rvyn/indie-toolkit/tree/main/dev-workflow/skills/execute-plan
Command: npx skills add https://github.com/n0rvyn/indie-toolkit --skill execute-plan-n0rvyn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning a verified implementation plan into executed work is error-prone when done manually, especially for long plans that may be interrupted or require user decisions mid-run. This Skill automates mechanical task execution in deterministic batches, tracks per-task progress, and surfaces blocked or failed tasks for human resolution.

Core Features & Use Cases

  • Batch Execution: Runs plan tasks in fixed 5-task batches to provide predictable progress checkpoints.
  • Verification Pre-checks: Ensures the plan contains a Verification section with a verdict before execution and can invoke verify-plan if needed.
  • Decision Point Handling: Detects unresolved decisions in the plan, prompts the user, and records chosen outcomes back into the plan file.
  • Stateful Resume & Truncation Recovery: Maintains a state file at .claude/execute-plan-state.json to resume after truncation or interruption.
  • Orchestrator Integration: Respects run-phase orchestration state and avoids stepping on orchestrator-owned transitions.

Quick Start

Execute the verified plan file to run implementation tasks in 5-task batches with automatic resume and an execution report.

Frequently Asked Questions about execute-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate plan execution for software development tasks?

Plan execution is automated by running verified implementation tasks in deterministic 5-task batches. This approach reduces manual orchestration by tracking per-task progress and surfacing blocked or failed items for human resolution.

What is truncation recovery in workflow orchestration?

Truncation recovery is a mechanism that resumes plan execution after interruptions by maintaining a state file at .claude/execute-plan-state.json. This ensures automated batch processing can continue from the last completed checkpoint.

Does plan execution require a verified plan file with a specific format?

Plan execution requires a verified plan file containing a Verification section with a verdict. The system performs verification pre-checks before execution and can invoke verify-plan if needed to ensure compliance.

How do I handle unresolved decision points during batch processing?

Batch processing detects unresolved decisions in the plan, prompts the user for input, and records the chosen outcomes directly back into the plan file. This ensures execution pauses appropriately for human-in-the-loop decisions.

What's the best way to run phased execution without overwriting orchestrator state?

Phased execution respects run-phase orchestration state by avoiding stepping on orchestrator-owned transitions. This ensures batch processing operates safely within the boundaries set by higher-level workflow orchestration.

Why does state management fail when executing long implementation plans manually?

State management fails manually due to error-prone tracking across long plans that require mid-run decisions or face interruptions. Automating task execution with a dedicated state file resolves this by providing reliable progress checkpoints.