openspec-auditlisted

Orchestrates a full compliance audit at one of five depths (quick, standard, strict, release, forensic) by composing openspec-verify, openspec-drift, and openspec-traceability. Use before /gsd-ship, or any time a broader confidence check is wanted than the per-phase verify:post step alone gives.
mshegolev/gsd-openspec-integration · ★ 0 · AI & Automation · score 73

Install: claude install-skill mshegolev/gsd-openspec-integration

## Purpose A single entry point for "how sure are we, really" at whatever depth the moment calls for — from a fast sanity check to a full forensic reconstruction of an existing, un-audited codebase. Composes the other skills; implements no verification logic of its own. ## Invocation conditions - Directly, any time: `/openspec-audit [quick|standard|strict|release|forensic]` (defaults to `workflow.openspec_audit_mode`, `standard`). - Recommended immediately before `/gsd-ship` on anything beyond a trivial phase, even though `ship:pre`'s gate only technically requires `openspec-verify`'s `status: passed`. ## Required inputs - Mode (one of the five below; defaults per config). - Scope: a single change-id, or "everything currently unshipped" (default). ## Files read Depends on mode — see table. Never writes to `openspec/` in any mode. ## Files this skill may write - `.planning/openspec/AUDIT-SUMMARY.md` (overwritten each run — it is a snapshot, not a log; `EVIDENCE.json` is the append-only log, written by `openspec-verify`/`openspec-traceability`) ## The five modes | Mode | Composes | Checks | |---|---|---| | **quick** | `openspec-verify` (cached, no re-run if fresh) | Task completion + targeted scenario tests only. Seconds, not minutes. | | **standard** | `openspec-verify` (fresh run) + `openspec-traceability` | Full requirement/scenario coverage + regression cross-reference (Levels 1-5 above). This is the default and what `ship:pre` effectively expects to have run rec