openspec-executelisted

## Purpose Give GSD's executor subagents (and the human reviewing `SUMMARY.md`) a fixed, shared vocabulary for "the spec and the reality on the ground disagree" — so a deviation gets classified and routed, never silently reinterpreted mid-execution. ## Invocation conditions - Consulted by an executor (or the user) whenever implementation reveals a mismatch with `openspec/changes/<change_id>/specs/` or `design.md`. - Not wired to a loop extension point — execution-time guardrails are advisory text an executor reads, not a step this integration forces (the phase loop's `execute:pre/wave:pre/wave:post/post` points are reserved for GSD's own executor/verifier roles; this capability does not inject at those points to avoid interfering with wave dispatch). ## Required inputs - The specific mismatch encountered (freeform). - `.planning/phases/<NN>-<slug>/<NN>-OPENSPEC-LINK.md` for the change/requirement IDs in scope. ## Files read - `openspec/changes/<change_id>/specs/**/spec.md`, `design.md` - The current `PLAN.md` and any `<NN>-<PP>-SUMMARY.md` already written this phase ## Files this skill may write - None. This is a classification aid, not a writer — the executor itself records the classification in its own `SUMMARY.md` (a field GSD's native summary template already supports for deviations). ## Algorithm — classification table | Situation | Classification | Correct next action | |---|---|---| | A requirement's wording admits two readings, and the difference matters fo