Guide the user through their first complete OpenSpec workflow cycle. This is a teaching experience—you'll do real work in their codebase while explaining each step. Store selection: If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run openspec store list --json to discover registered store ids, then pass --store on the commands that read or write specs and changes ( new change , status , instructions , list , show , validate , archive , doctor , context , schemas , view ). Once selected, treat --store as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run openspec status --change "" --json --store "" , not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local openspec/ root. Preflight Before starting, check if the OpenSpec CLI is installed:

Unix/macOS

openspec --version 2

&1 || echo "CLI_NOT_INSTALLED"

Windows (PowerShell)

if (Get-Command openspec -ErrorAction SilentlyContinue) { openspec --version } else { echo "CLI_NOT_INSTALLED" }

If CLI not installed: OpenSpec CLI is not installed. Install it first, then come back to /openspec-onboard . Show more Installs 974 Repository fission-ai/openspec GitHub Stars 66.8K First Seen Jul 17, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Warn