Propose a new change - create the change and generate all artifacts in one step.

I'll create a change with artifacts:

• proposal.md (what & why)
• design.md (how)
• tasks.md (implementation steps)

When ready to implement, run /opsx:apply

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 <id> on the commands that read or write specs and changes (new change, status, instructions, list, show, validate, archive, doctor, context). 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.

Input: The user's request should include a change name (kebab-case) OR a description of what they want to build.

Precondition — the plan gate. Run it first, before creating anything.

No change may start without an approved entry in openspec/PLAN.md. Once you have the change name, and before openspec new change or any artifact:

bash scripts/check-plan-gate.sh --change "<name>"

• Exit 0 → proceed with the steps below.
• Non-zero exit → stop. Create nothing — no change directory, no proposal, no spec, no tasks — and quote the script's reason verbatim: NO-ENTRY, NOT-APPROVED, HASH-MISMATCH or STALE. Do not paraphrase it; the reason names the fix. Then hand over to plan-mode, which owns the plan. NO-ENTRY on work the user clearly wants is not a formality: it means the work is not in the plan, and adding an entry is the user's call, not yours.
• If the change name is not yet known, ask for it. Never invent or guess a name to satisfy --change — a made-up name passes the flag and defeats the check.
• If scripts/check-plan-gate.sh is missing or not executable, say so and stop: report that the plan gate is not installed in this project and that spec-as-source-setup installs it. A check that cannot run is not an approval, and treating it as one is indistinguishable from an approved plan.

Run the script; do not re-implement it. This skill never reads openspec/PLAN.md, never inspects entries or their approval fields, and never computes or compares an approval hash: scripts/check-plan-gate.sh is the only judge and the only implementation of the hash. ROUTER.md § Stage 2B runs the same command before routing here — same script, same reasons, one gate at two doors, so the routed path and a direct invocation of this skill cannot disagree.

Steps

1. If no clear input provided, ask what they want to build

   Ask the user, open-ended (no preset options):

   "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.

2. Create the change directory — only after the plan gate above exited 0

   openspec new change "<name>"

   This creates a scaffolded change in the planning home resolved by the CLI with .openspec.yaml.

3. Get the artifact build order

   openspec status --change "<name>" --json

   Parse the JSON to get:

   • applyRequires: array of artifact IDs needed before implementation (e.g., ["tasks"])
   • artifacts: list of all artifacts with their status and dependencies
   • planningHome, changeRoot, artifactPaths, and actionContext: path and scope context. Use these instead of assuming repo-local paths.

4. Create artifacts in sequence until apply-ready

   Track progress through the artifacts with a todo list (or your environment's equivalent progress-tracking mechanism).

   Loop through artifacts in dependency order (artifacts with no pending dependencies first):

   a. For each artifact that is ready (dependencies satisfied):

   • Get instructions:

     openspec instructions <artifact-id> --change "<name>" --json

   • The instructions JSON includes:
     • context: Project background (constraints for you - do NOT include in output)
     • rules: Artifact-specific rules (constraints for you - do NOT include in output)
     • template: The structure to use for your output file
     • instruction: Schema-specific guidance for this artifact type
     • resolvedOutputPath: Resolved path or pattern to write the artifact
     • dependencies: Completed artifacts to read for context
   • Read any completed dependency files for context
   • Create the artifact file using template as the structure and write it to resolvedOutputPath
   • Apply context and rules as constraints - but do NOT copy them into the file
   • Show brief progress: "Created "

   b. Continue until all applyRequires artifacts are complete

   • After creating each artifact, re-run openspec status --change "<name>" --json
   • Check if every artifact ID in applyRequires has status: "done" in the artifacts array
   • Stop when all applyRequires artifacts are done

   c. If an artifact requires user input (unclear context):

   • Ask the user to clarify
   • Then continue with creation

5. Show final status

   openspec status --change "<name>"

Output

After completing all artifacts, summarize:

• Change name and location
• List of artifacts created with brief descriptions
• What's ready: "All artifacts created! Ready for implementation."
• Prompt: "Run /opsx:apply or ask me to implement to start working on the tasks."

Artifact Creation Guidelines

• Follow the instruction field from openspec instructions for each artifact type
• The schema defines what each artifact should contain - follow it
• Read dependency artifacts for context before creating new ones
• Use template as the structure for your output file - fill in its sections
• IMPORTANT: context and rules are constraints for YOU, not content for the file
  • Do NOT copy <context>, <rules>, <project_context> blocks into the artifact
  • These guide what you write, but should never appear in the output

Guardrails

• Create ALL artifacts needed for implementation (as defined by schema's apply.requires)
• Always read dependency artifacts before creating a new one
• If context is critically unclear, ask the user - but prefer making reasonable decisions to keep momentum
• If a change with that name already exists, ask if user wants to continue it or create a new one
• Verify each artifact file exists after writing before proceeding to next