lcp-execplan

Create and maintain ExecPlans for complex work (design-to-implementation) following the repo's ExecPlan standard.

⭐2stars🔀0forks📁View on GitHub🕐Updated Jan 8, 2026

When & Why to Use This Skill

This Claude skill provides a structured framework for creating and maintaining Execution Plans (ExecPlans) for complex software engineering tasks. It bridges the gap between initial design and final implementation by enforcing a standardized, milestone-driven workflow that tracks progress, technical decisions, and discoveries in real-time, ensuring high-quality outcomes for ambiguous requirements.

Use Cases

  • Complex Feature Development: Streamline the transition from design to code by generating a detailed, milestone-based roadmap that ensures all technical requirements are met.
  • Large-scale Code Refactoring: Manage high-risk architectural changes by maintaining a living document that captures critical decisions and prevents scope creep during execution.
  • Ambiguous Requirement Resolution: Use the ExecPlan as a source of truth to clarify project goals and document evolving technical strategies as the implementation progresses.
  • Standardized Team Workflows: Enforce repository-specific standards for project execution, enabling any developer to reproduce working outcomes based on the stored plan.
namelcp-execplan
descriptionCreate and maintain ExecPlans for complex work (design-to-implementation) following the repo's ExecPlan standard.
short-descriptionExecPlan workflow (design → implementation)

Use this skill when the task is a complex feature, a significant refactor, or has ambiguous requirements that benefit from a living plan.

Source of truth

The ExecPlan standard for this repo is in:

  • .codex/skills/lcp-execplan/references/PLANS.md

Workflow

  1. Read the full reference PLANS.md above (it is intentionally strict).
  2. Create a single ExecPlan file as instructed (formatting rules matter).
  3. Keep the ExecPlan as a living document: update Progress/Decisions/Discoveries as you implement.
  4. Do not ask the user for “next steps” mid-execution; proceed milestone by milestone.

Acceptance

An ExecPlan is done only when it enables a complete novice (with only the repo + the plan) to reproduce a working, observable outcome.