execplans

Name: execplans
Availability: InStock
Author: Leynos

Create living design-and-delivery documents for end-to-end repo changes.

2|1|Updated Jun 13, 2025

Search Tags:#planning #execution #end-to-end #software #design-doc #execplan #repo-changes

Ready to run

npx skills add https://github.com/leynos/agent-helper-scripts --skill execplans

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: execplans
Source: https://github.com/leynos/agent-helper-scripts/tree/main/skills/execplans
Command: npx skills add https://github.com/leynos/agent-helper-scripts --skill execplans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ExecPlans provide a living, self-contained design-and-delivery document that guides novices to ship a demonstrably working change.

Core Features & Use Cases

Living document that evolves with progress and discoveries.
End-to-end guidance including validation, milestones, and observable outcomes.
Plain-language definitions and escalation rules to prevent scope creep.

Quick Start

Draft a complete ExecPlan that is self-contained, verifiable, and ready for user approval.

Frequently Asked Questions about execplans

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

FAQPage Schema

How do I create a design doc that guides end-to-end software implementation?▼

To create an end-to-end software implementation design doc, draft a self-contained ExecPlan that includes validation, milestones, and observable outcomes. The document must use plain language to guide novices through shipping a demonstrably working repo change.

What is the best way to plan meaningful repo changes with observable outcomes?▼

The best way to plan meaningful repo changes is using a living, self-contained ExecPlan. It evolves with progress, defines clear boundaries, includes end-to-end validation, and ensures delivery of a demonstrably working change through controlled delegation.

How do I prevent scope creep during end-to-end software delivery?▼

Prevent scope creep during end-to-end software delivery by using an ExecPlan with plain-language definitions and explicit escalation rules. These boundaries keep the implementation focused on observable outcomes rather than expanding requirements.

When do I need a living document for software execution planning?▼

You need a living document for software execution planning when implementing meaningful repo changes that require end-to-end guidance. It is essential when updates must reflect ongoing discoveries and novices need to ship demonstrably working changes.

Can I use execution plans for end-to-end validation of repository changes?▼

Yes, you can use execution plans for end-to-end validation of repository changes. ExecPlans are specifically designed to include validation steps and observable outcomes, ensuring the implementation is demonstrably working before delivery.

Are ExecPlans suitable for novices shipping demonstrably working code changes?▼

Yes, ExecPlans are suitable for novices shipping demonstrably working code changes. They provide a self-contained design-and-delivery document with plain-language guidance and a controlled delegation model to facilitate end-to-end implementation.