dev.exec-plan

Generate structured Markdown execution plans for complex development tasks.

6|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/kevinslin/llm --skill dev-exec-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev.exec-plan
Source: https://github.com/kevinslin/llm/tree/main/skills/dev.exec-plan
Command: npx skills add https://github.com/kevinslin/llm --skill dev-exec-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

The Execution Plan Skill creates structured, file-based execution plans for complex development tasks, enabling persistent documentation and a clear path from idea to implementation.

Core Features & Use Cases

  • Template-driven plans: Generate plan documents that include Goal, Context, Technical Approach, Steps, Dependencies, Risks, and Questions.
  • Persistent documentation: Save plans as Markdown files in a designated plan directory for long-term reference.
  • Review-ready artifacts: Produce plans suitable for stakeholder review and approval before work begins.

Quick Start

Create a new execution plan in the active plans directory using the plan-template and save it under a descriptive filename.

Frequently Asked Questions about dev.exec-plan

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

FAQPage Schema
How do I create an execution plan for a complex development task with multiple milestones?

Structured execution plans are file-based Markdown documents that outline goals, context, technical approach, steps, dependencies, risks, and review criteria for complex development tasks. They provide persistent documentation and a clear path from idea to implementation.

What should be included in a development plan template for architectural decisions?

Use a template-driven execution plan when working on architectural decisions, multi-phase work, tasks with external dependencies, or any request requiring documented strategy and milestones for stakeholder approval before implementation begins.

How do I document technical approaches and risks for multi-phase development work?

Execution plans are suitable for stakeholder review because they follow a template-driven approach that explicitly documents goals, context, technical method, steps, dependencies, risks, and review criteria before any development work begins.

When do I need a structured execution plan for a software engineering project?

Execution plans are best suited for complex development tasks requiring documented strategy, multi-phase coordination, or external dependency management. For simple, single-step tasks, lightweight documentation may be more appropriate than a full template-driven plan.