execplan

Create and maintain executable specifications in PLANS.md for feature delivery.

59|4|Updated Dec 2, 2025
One-click install
npx skills add https://github.com/lanegrid/agtrace --skill execplan-lanegrid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execplan
Source: https://github.com/lanegrid/agtrace/tree/main/.agent/skills/execplan
Command: npx skills add https://github.com/lanegrid/agtrace --skill execplan-lanegrid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ExecPlans provide a self-contained executable specification that guides feature delivery from concept to working results, and records decisions for posterity.

Core Features & Use Cases

  • Fully self-contained ExecPlans: living documents that evolve with project progress and discoveries.
  • Milestone-driven guidance: clear phases with decisions logged, enabling reproducible implementation.
  • Real-world applicability: used when designing complex features or major refactors to ensure alignment and traceability.

Quick Start

Start a new ExecPlan by creating a self-contained document following PLANS.md, begin with a feature skeleton, add milestones as you progress, and commit decisions to the log.

Frequently Asked Questions about execplan

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

FAQPage Schema
How do I create executable specifications for complex feature delivery?

You create executable specifications by building self-contained ExecPlan documents that guide feature delivery from concept to working results, embedding completion criteria, milestones, and rationale within PLANS.md contexts.

What is an ExecPlan and how does it work for major refactors?

An ExecPlan is a self-contained executable specification that guides major refactors by providing milestone-driven phases with logged decisions, ensuring reproducible implementation and traceable feature delivery.

How do I maintain feature documentation that a novice developer can follow?

Maintain novice-friendly feature documentation by using ExecPlans to ensure plans are self-contained with upfront completion criteria, embedded rationale, and milestone-driven guidance recorded within PLANS.md contexts.

When do I need milestone-driven planning for software projects?

You need milestone-driven planning when designing complex features or major refactors across software projects, where it provides alignment, traceability, and a living record of decisions from skeleton to working implementation.

Does ExecPlan work without external dependencies for tracking project decisions?

ExecPlan operates without external dependencies, using PLANS.md contexts to track decisions by committing them to a log within the self-contained document, ensuring traceable and reproducible implementation.

What is the best way to document feature skeletons and completion criteria?

The best way to document feature skeletons and completion criteria is through ExecPlans, which start with a feature skeleton, add milestones as you progress, and embed rationale to create a living record of decisions.