Menu
Start a new change using the experimental artifact workflow (OPSX)
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when proposing or reviewing BK-Lite operations-product modules, MVP scope, product specifications, competitor-derived designs, workflow/state models, extensibility decisions, permissions, audit, execution safety, or acceptance criteria.
Archive multiple completed changes at once
Continue working on a change - create the next artifact (Experimental)
Create a change and generate all artifacts needed for implementation in one go
Guided onboarding - walk through a complete OpenSpec workflow cycle with narration
Sync delta specs from a change to main specs
| name | source-command-opsx-new |
| description | Start a new change using the experimental artifact workflow (OPSX) |
Use this skill when the user asks to run the migrated source command opsx-new.
Start a new change using the experimental artifact-driven approach.
Input: The argument after /opsx:new is the change name (kebab-case), OR a description of what the user wants to build.
Steps
If no input provided, ask what they want to build
Use the AskUserQuestion tool (open-ended, no preset options) to ask:
"What change do you want to work on? Describe what you want to build or fix."
From their description, derive a kebab-case name (e.g., "add user authentication" → add-user-auth).
IMPORTANT: Do NOT proceed without understanding what the user wants to build.
Determine the workflow schema
Use the default schema (omit --schema) unless the user explicitly requests a different workflow.
Use a different schema only if the user mentions:
--schema <name>openspec schemas --json and let them chooseOtherwise: Omit --schema to use the default.
Create the change directory
openspec new change "<name>"
Add --schema <name> only if the user requested a specific workflow.
This creates a scaffolded change at openspec/changes/<name>/ with the selected schema.
Show the artifact status
openspec status --change "<name>"
This shows which artifacts need to be created and which are ready (dependencies satisfied).
Get instructions for the first artifact The first artifact depends on the schema. Check the status output to find the first artifact with status "ready".
openspec instructions <first-artifact-id> --change "<name>"
This outputs the template and context for creating the first artifact.
STOP and wait for user direction
Output
After completing the steps, summarize:
/opsx:continue or just describe what this change is about and I'll draft it."Guardrails
/opsx:continue instead