exec-plans-standardlisted

# Exec-Plans Standard This is a meta-skill: a rule that applies to a specific, recurring document type — the ExecPlan — used across this knowledge base's Design, Implementation, and other stages whenever a change is complex enough to need a persistent, revisable plan. The rules below are read live from this plugin's own `skills/exec-plans-standard/exec-plans-standard.md` every time this skill runs, so there is no separate paraphrased copy anywhere for this content to drift against. ## Exec-plans standard (live) !`cat "${CLAUDE_PLUGIN_ROOT}/skills/exec-plans-standard/exec-plans-standard.md"` ## Instructions 1. When authoring a new ExecPlan, start from the Skeleton Of A Good ExecPlan above and flesh out every section with real content — do not skip a section because it feels premature; an ExecPlan without `Progress`, `Surprises & Discoveries`, `Decision Log`, and `Outcomes & Retrospective` is not a valid ExecPlan under this standard, per the Living Plans And Design Decisions section above. 2. Treat self-containment as non-negotiable: a reader with only the current working tree and this one file, no memory of prior conversation, must be able to follow it end-to-end. Define every term of art in plain language the first time you use it; do not write "as defined previously" or point to an external doc for meaning that must live in the plan itself. 3. When executing or continuing work under an existing ExecPlan, do not stop to ask "what's next" — proceed to the next milestone,