opsx-propose

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

---

Input: The argument after /opsx-propose is the change name (kebab-case), OR a description of what the user wants to build.

Steps

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

2. Create the change directory

   openspec new change "<name>"
   

   This creates a scaffolded change at openspec/changes/<name>/ with .openspec.yaml.

2a. Check for uncommitted changes

Before creating or switching branches, run git status --short. If there are uncommitted changes (staged, unstaged, or untracked files that appear related to work):

• STOP and ask the user for confirmation before switching branches. Show what uncommitted changes exist and warn that switching branches with a dirty working tree may cause changes to be applied to the wrong branch.
• If the user confirms, proceed. If not, abort.
• Exception: if the user explicitly requested a new change, this still requires confirmation -- never silently switch branches with uncommitted work.

2b. Create and checkout a branch

git checkout -b opsx/<name>

Guard: Before creating the branch, check the current branch:

• If already on opsx/<name> (exact match): skip branch creation, proceed.
• If on a different opsx/* branch: STOP with error: "Already on branch opsx/<other> -- finish or archive that change first."
• If on main or any non-opsx branch: create and checkout opsx/<name>.

2c. Retrieve context from Dewey

Before drafting the proposal, query Dewey for relevant context:

• dewey_semantic_search with the change description to find related specs, past proposals, and similar changes
• dewey_semantic_search_filtered with source_type: "github" to find related issues across the organization
• dewey_traverse on any discovered related specs to understand dependencies

Use the retrieved context to inform the proposal's scope, identify potential conflicts with existing work, and reference relevant prior decisions.

If Dewey is unavailable, proceed without cross-repo context -- use direct file reads of local specs and backlog items instead.

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

2. Create artifacts in sequence until apply-ready

   Use the TodoWrite tool to track progress through the artifacts.

   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
     • outputPath: Where 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
   • Apply context and rules as constraints - but do NOT copy them into the file
   • Show brief progress: "Created "