Exec Plan

This is workflow infrastructure for managing multi-step work that spans sessions or touches more than three files. It enforces a living document format with sections for progress tracking, surprises, decisions, and validation commands. The format is deliberately narrative, not a checklist: it captures why changes matter, what the codebase looks like now, and how to prove success. The real discipline is updating progress immediately after each milestone with timestamps, because that's your only persistence between sessions. Plans live in docs/exec-plans/active until complete, then move to completed. If you're doing anything non-trivial, this keeps you from redoing work or losing context when you pick it back up tomorrow.

skills.sh installs: 232
GitHub stars: 222
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add pproenca/dot-skills --skill exec-plan --agent claude-code

Installs into .claude/skills of the current project.

Files

ExecPlan — Lifecycle Management

Announce at start: "Using the exec-plan skill."

What is an ExecPlan

A self-contained, living document that a fresh agent session can follow to deliver observable, working behavior. Lives in docs/exec-plans/. The format follows the specification in docs/PLANS.md.

An ExecPlan is NOT a todo list. It is a narrative that tells the story of a change: why it matters, what the codebase looks like now, what it should look like after, and how to prove it worked.

When to use this skill

Required for multi-step or multi-file work, new features, refactors, or tasks expected to take more than about an hour.
Optional for trivial fixes, but if you skip it for a substantial task, state the reason.
Always when resuming work from a previous session.