openspec-verifylisted

## Purpose This is the one skill the whole integration's "Ship is blocked until proven" guarantee rests on. It reads what GSD's own verifier already produced (`VERIFICATION.md`, `SUMMARY.md`) plus OpenSpec's own state (`openspec validate --json`) and produces a second, OpenSpec-specific verdict — never re-deriving GSD's own must_haves check, only adding the OpenSpec compliance dimension GSD has no native concept of. ## Invocation conditions - Automatically at `verify:post`, when `workflow.openspec_verification` is true and `<NN>-OPENSPEC-LINK.md` exists for the phase. - Directly, for a spot re-check without re-running the whole `/gsd-verify-work` step. ## Required inputs - `<NN>-OPENSPEC-LINK.md` (change_id, requirement_ids, scenario_ids) - `<NN>-SUMMARY.md` (one per plan, produced by execute-phase — this step's `consumes`) - `<NN>-VERIFICATION.md` (GSD's own core verifier output, if present — read-only cross-reference, never modified) ## Files read - `openspec/changes/<change_id>/specs/**/spec.md`, `design.md` - All `<NN>-<PP>-SUMMARY.md` and `<NN>-VERIFICATION.md` for the phase - Git log/diff for the phase's commits (`git log --oneline <phase-start-ref>..HEAD`) - The project's actual test output (whatever `SUMMARY.md`/`VERIFICATION.md` already cite — this skill does not re-run tests itself; it verifies evidence already produced, per the "no fabricated test results" guardrail) ## Files this skill may write - `<NN>-OPENSPEC-VERIFICATION.md` (this step's sole output a