exec-plan

Create living execution plans with milestones, acceptance criteria, and decision logs.

3|1|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/indrasvat/claude-code-skills --skill exec-plan-indrasvat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: exec-plan
Source: https://github.com/indrasvat/claude-code-skills/tree/main/skills/exec-plan
Command: npx skills add https://github.com/indrasvat/claude-code-skills --skill exec-plan-indrasvat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a self-contained, living execution plan that guides a stateless agent or developer through complex work without prior context, ensuring repeatable, auditable progress.

Core Features & Use Cases

  • Living document: evolves as discoveries and decisions are made, preserving traceability.
  • Milestone-driven work: defines discrete steps with exact commands, inputs, and expected outputs.
  • Plan portability: usable by humans or agents across contexts without reengineering.
  • Decision Log & Recovery: maintains decisions, rationale, and rollback guidance for resilience.

Quick Start

Create a new ExecPlan under plans/ named after the task and begin populating milestones with clear, idempotent steps and acceptance criteria.

Frequently Asked Questions about exec-plan

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

FAQPage Schema
What is a self-contained execution plan and when do I need one for software projects?

A self-contained execution plan is a living document that guides stateless agents or developers through complex work without prior context. You need one for multi-phase initiatives requiring repeatable, auditable progress and traceability.

How do I create a living execution plan with milestones and acceptance criteria?

Create a new plan under the plans/ directory named after your task, then populate milestones with discrete, idempotent steps, explicit inputs, expected outputs, and exact acceptance criteria to guide autonomous agents or developers.

How does milestone-driven plan management handle unknowns and risks during development?

Milestone-driven plan management handles unknowns by enforcing spike handling for technical discoveries and maintaining a decision log with rationale and rollback guidance, ensuring resilience and recovery during complex software project execution.

Can I use this execution plan format for both autonomous agents and human developers?

Yes, the execution plan is portable and usable by humans or agents across contexts without reengineering. It provides exact commands and explicit acceptance criteria, ensuring stateless agents and developers can execute complex work consistently.

What is the best way to track progress and decisions in a multi-phase workflow plan?

The best way to track progress is using a living document that evolves with discoveries, maintaining a decision log for rationale and rollback guidance. This ensures traceability and repeatable, auditable progress throughout the workflow.

Why do I need idempotent steps and validation in plan management?

Idempotent steps and validation are needed in plan management to ensure repeatable execution without side effects. By defining discrete steps with exact commands and expected outputs, the plan enforces auditable progress and safe recovery.