write-exec-plan

Write evidence-backed execution plans with prototype validation and phased verification checklists.

2|Updated Sep 14, 2026
One-click install
npx skills add https://github.com/kwanpham2195/agent-stuff --skill write-exec-plan-kwanpham2195
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-exec-plan
Source: https://github.com/kwanpham2195/agent-stuff/tree/main/skills/write-exec-plan
Command: npx skills add https://github.com/kwanpham2195/agent-stuff --skill write-exec-plan-kwanpham2195

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Complex multi-phase work often fails because plans commit to implementation before resolving technical unknowns, leaving reviewers unable to audit progress. This Skill produces restartable execution plans where consequential questions are settled by bounded prototypes first, and every phase checkbox names concrete evidence. ## Core Features & Use Cases - Prototype-first planning: Identify consequential technical questions and resolve them with small, bounded experiments before drafting implementation phases. - Evidence-backed phase checklists: Each phase defines build steps, automated checks, live verification, performance budgets, and human review gates with named evidence artifacts. - Plan maintenance during execution: Update plans through authorized execution, checkpoint progress, and revise phases when assumptions fail. - Use Case: Before migrating a notification system across three PRs, use this Skill to prototype the risky state-management integration, record the verdict, then draft a phased plan with verification commands and review gates for approval. ## Quick Start Use the write-exec-plan skill to prototype the uncertain integration points and draft a phased, evidence-backed execution plan for my migration project.

Frequently Asked Questions about write-exec-plan

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

FAQPage Schema
How do I write an execution plan for a complex multi-phase project?▼

Start by listing consequential technical questions and resolving each with a small bounded prototype. Then draft one phase per independently verifiable outcome, with build steps, automated checks, live verification, and evidence named for every checkbox.

How to plan work when technical feasibility is uncertain?▼

Define the smallest experiment with a pass/fail observation and a time or resource boundary for each unresolved question. Run the probe, record the verdict and limitations, and only then commit dependent phases to the plan.

When should I not use a formal execution plan?▼

Skip the durable plan when the change is small with an obvious approach; an inline sequence is sufficient. The Skill itself recommends stopping unless the user still wants a durable, auditable plan.

Does creating an execution plan authorize implementation?▼

No. A planning request ends with the plan handed back for review and does not authorize branches, commits, deployments, or external writes. Execution authority must be granted separately and existing authority resumes only after review gates clear.

What happens when a prototype refutes the planned approach?▼

Revise the approach and probe the remaining question, stopping when the question is answered or a stated bound is reached. If blocked, return a clearly marked blocked or provisional plan naming the missing evidence and next action.