openspec-init

Topics in the source

• Step 1 — Resolve the CLI (set OPENSPECCMD)
• Step 2 — Check repo state
• Step 3 — Initialize (absent)
• Step 4 — Repair (invalid)
• Step 5 — Verify and stage

Bring the current repo to a valid OpenSpec state: the openspec CLI resolvable and an openspec/ corpus (specs/ + changes/) present and healthy. Corpus only — no /opsx: slash commands or AGENTS wiring, because the /la:pr flow replaces propose/apply. 1. If command -v openspec succeeds → OPENSPECCMD=openspec. 2. Else install globally: npm i -g @fission-ai/openspec (no sudo where the npm global prefix is user-writable — nvm/fnm//.local-style node). Re-check command -v openspec. 3. If the global install fails (non-writable prefix, no permission, or offline): fall back to OPENSPECCMD="npx -y @fission-ai/openspec@1.11.0" (bump the pin as needed). If even npx can't fetch, STOP and tell me — do not proceed. Use $OPENSPECCMD for every openspec call below and hand it back to the caller. Run from the repo root (init writes openspec/ into the cwd). Classify: Absent — no openspec/config.yaml → Step 3. Healthy — openspec/config.yaml exists and $OPENSPECCMD list runs cleanly → nothing to do; report and return. (A healthy repo may have no specs/ or changes/ yet — see Step 3 — so their absence is NOT invalid.) Invalid — openspec/ exists but has no config.yaml, or list/doctor errors → Step 4. Add --fo

This is an excerpt. Refer to the complete source and its current requirements.