mshegolev
UserGSD Core capability making OpenSpec the normative requirement source for the GSD phase loop — ship is blocked until implementation is proven to satisfy it.
Categories
Indexed Skills (11)
openspec-archive
The post-ship closing step — runs OpenSpec's own archive to fold a shipped change's deltas into the living specs, refreshes the final traceability snapshot, and syncs GSD's STATE.md with what actually shipped. Runs only after ship succeeded; archiving is never a way to make a gate pass.
openspec-audit
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.
openspec-bootstrap
One-time setup that installs OpenSpec into a project already (or about to be) managed by GSD Core, scaffolds this capability's integration state, and explains the unified lifecycle. Use when starting /gsd-new-project or /gsd-onboard on a project that doesn't have openspec/ yet, or when a user asks to "add OpenSpec to this GSD project".
openspec-bridge-explore
Bridges OpenSpec's own /opsx:explore into the GSD entry point — use before /gsd-discuss-phase when the user has an idea but no OpenSpec change yet. Does not replace OpenSpec's explore skill; it just makes sure exploration output lands where GSD's discuss:pre check will find it.
openspec-bridge-propose
Ensures a GSD phase has a valid, complete OpenSpec change (proposal+specs+design+tasks) before /gsd-discuss-phase or /gsd-plan-phase will proceed. Wraps native /opsx:propose (or /opsx:ff for the expanded profile) and validates the result, rather than reimplementing artifact generation.
openspec-drift
The Level 6 spec-drift audit — cross-references OpenSpec against GSD plans, git diff, tests, and evidence to find the nine drift classes (requirement without implementation, code without requirement, closed task with no diff, behavior change with no spec delta, and so on). Consumed by openspec-verify for its roll-up and by openspec-audit in strict mode and above.
openspec-execute
Scope guardrail and deviation classifier consulted during /gsd-execute-phase when a phase has a linked OpenSpec change. Not an executor itself — GSD's own executor subagents write the code; this skill only classifies what to do when an executor's discovery doesn't match the locked spec.
openspec-plan
Syncs OpenSpec requirements into GSD's REQUIREMENTS.md (REQ-ID projection), maps OpenSpec tasks.md to the phase's PLAN.md files, and answers the plan:post agentVerdict gate (scenario coverage check). Runs as part of /gsd-plan-phase for any phase with an OPENSPEC-LINK.md.
openspec-repair
Turns a classified gap — from openspec-verify, openspec-drift, or an executor's deviation tag — into a concrete, routed fix plan. Decides which of the four repair routes a gap takes (fix the code, update the spec, open a new change, or block), and never resolves a gap by weakening what was agreed.
openspec-traceability
Assigns and maintains stable requirement/scenario IDs that OpenSpec has no native concept of, then generates the TRACEABILITY.md matrix and the machine-readable EVIDENCE.json log. The one skill in this capability permitted to write inside openspec/ — and only ever to add an inert HTML-comment ID line, never to touch requirement text.
openspec-verify
Wired as the verify:post step. Produces OPENSPEC-VERIFICATION.md, the evidence-backed compliance report the ship:pre gate blocks on. Runs six verification levels — task, scenario, requirement, design compliance, regression, spec-drift — and never marks anything PASS without a cited artifact.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.