openspec-bootstraplisted

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".
mshegolev/gsd-openspec-integration · ★ 0 · AI & Automation · score 73

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

## Purpose Make a project OpenSpec-and-GSD-ready in one idempotent pass: install the OpenSpec CLI's project scaffold, install this capability, and create the integration-owned state directories — without touching anything GSD or OpenSpec already own. ## Invocation conditions - Explicitly via `/gsd-new-project` or `/gsd-onboard` (this capability's `discuss:pre` fragment will otherwise nag on every phase without it). - Directly, any time, by a user or agent that wants to (re-)check the setup — it is safe to run repeatedly. ## Required inputs - None. Reads the current working directory as the project root. ## Files read - `openspec/` (existence check only) - `.planning/` (existence check only) - `.gsd-capabilities.json` (existence + whether `openspec` is already installed) ## Files this skill may write - `openspec/` (via `openspec init`, if absent) — never overwrites an existing `openspec/` - `.planning/openspec/` (`id-registry.json`, `TRACEABILITY.md`, `EVIDENCE.json`, `AUDIT-SUMMARY.md` — created empty/seeded, never overwritten if present) - Nothing under `.planning/phases/`, `.planning/PROJECT.md`, `.planning/ROADMAP.md`, `.planning/STATE.md` — those are GSD's own and this skill only reads them if present ## Algorithm 1. Check `command -v openspec`. If absent, stop and tell the user to run `npm install -g @fission-ai/openspec@latest` — do not attempt a project-local install of a global CLI tool. 2. If `openspec/` does not exist: run `openspec init --tools claude,co