Superspec Research

Rules (non-negotiable)

• Drive OpenSpec via CLI only (NO OpenSpec slash commands; i.e., commands starting with /opsx or /openspec).
• Prefer JSON output for every OpenSpec call that supports it (use --json).
  • If a required command does not support --json (e.g., openspec new change), run it without --json and continue with the next JSON-capable command (typically openspec status --change <change> --json).
• Keep changes scoped to proposal and specs artifacts only.
• If proposal is not complete, run the brainstorming prelude before writing proposal.md (see skills/superspec-brainstorm/SKILL.md).

Change Selection

1. If the user provides a change name, use it as <change>.
2. Else run:
   • openspec list --json Ask the user to confirm/select a change name from the JSON output.
3. If there are no changes (or user wants a new one), ask for:
   • change name (kebab-case)
   • one-sentence description Then run:
   • openspec new change <change> --schema superspec-rpi --description "<description>"