lcp-execplan

Create executable ExecPlans with PLANS.md sections and formatting.

2|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/YusukeShimizu/lightning-compute-protocol --skill lcp-execplan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lcp-execplan
Source: https://github.com/YusukeShimizu/lightning-compute-protocol/tree/main/.codex/skills/lcp-execplan
Command: npx skills add https://github.com/YusukeShimizu/lightning-compute-protocol --skill lcp-execplan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

ExecPlans provide a precise, executable blueprint for complex repo work, turning ambiguous requirements into a living, testable plan that novices can follow.

Core Features & Use Cases

  • Living ExecPlan: Create a self-contained document that evolves as decisions are made and progress is tracked.
  • Milestones & Decisions: Record milestones, decisions, and discoveries to guide future work and onboarding.
  • Reproducible Implementation: Enable a novice to reproduce a feature end-to-end by following the plan.

Quick Start

Start by creating a single ExecPlan file in the repository root that follows PLANS.md structure and includes Progress, Surprises & Discoveries, Decision Log, and Outcomes sections, then update it as work proceeds.

Frequently Asked Questions about lcp-execplan

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

FAQPage Schema
How do I create a living document for complex software development work?

A living document for software development is an ExecPlan that evolves by tracking milestones, decisions, and discoveries. You create it by structuring a single file with Progress, Surprises & Discoveries, Decision Log, and Outcomes sections.

What's the best way to turn ambiguous project requirements into a reproducible implementation plan?

To turn ambiguous requirements into reproducible implementation plans, craft an executable ExecPlan. This blueprint records milestones and decisions, enabling novices to reproduce features end-to-end by following the structured guidelines.

How do I track design-to-implementation decisions and progress in a repository?

Track design-to-implementation decisions by maintaining an ExecPlan with a Decision Log and Progress section. This living document in the repository root captures milestones and discoveries, guiding future work and onboarding.

What sections are required for an ExecPlan in a software project?

Required ExecPlan sections include Progress, Surprises & Discoveries, Decision Log, and Outcomes & Retrospective. These sections are enforced by the PLANS.md reference to ensure the plan remains a living, testable blueprint.

Do I need a PLANS.md file to use an ExecPlan for my project milestones?

Yes, you need a PLANS.md file in the repository. The ExecPlan requires this reference to enforce its strict formatting guidelines and the required sections for tracking progress, decisions, and retrospective outcomes.

Can a novice developer reproduce a feature by following an ExecPlan?

Yes, a novice can reproduce a feature end-to-end. ExecPlans provide a precise, executable blueprint that transforms ambiguous requirements into a living, testable plan with clear milestones for anyone to follow.