1---2name: openspec-continue-change3description: Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.4license: MIT5compatibility: Requires openspec CLI.6metadata:7 author: openspec8 version: "1.0"9 generatedBy: "1.4.1"10---1112Continue working on a change by creating the next artifact.1314**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.1516**Steps**17181. **If no change name provided, prompt for selection**1920 Run `openspec list --json` to get available changes sorted by most recently modified. Then use the **AskUserQuestion tool** to let the user select which change to work on.2122 Present the top 3-4 most recently modified changes as options, showing:23 - Change name24 - Schema (from `schema` field if present, otherwise "spec-driven")25 - Status (e.g., "0/5 tasks", "complete", "no tasks")26 - How recently it was modified (from `lastModified` field)2728 Mark the most recently modified change as "(Recommended)" since it's likely what the user wants to continue.2930 **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.31322. **Check current status**33 ```bash34 openspec status --change "<name>" --json35 ```36 Parse the JSON to understand current state. The response includes:37 - `schemaName`: The workflow schema being used (e.g., "spec-driven")38 - `artifacts`: Array of artifacts with their status ("done", "ready", "blocked")39 - `isComplete`: Boolean indicating if all artifacts are complete40 - `planningHome`, `changeRoot`, `artifactPaths`, and `actionContext`: path and scope context. Use these instead of assuming repo-local paths.41423. **Act based on status**:4344 ---4546 **If all artifacts are complete (`isComplete: true`)**:47 - Congratulate the user48 - Show final status including the schema used49 - Suggest: "All artifacts created! You can now implement this change or archive it."50 - STOP5152 ---5354 **If artifacts are ready to create** (status shows artifacts with `status: "ready"`):55 - Pick the FIRST artifact with `status: "ready"` from the status output56 - Get its instructions:57 ```bash58 openspec instructions <artifact-id> --change "<name>" --json59 ```60 - Parse the JSON. The key fields are:61 - `context`: Project background (constraints for you - do NOT include in output)62 - `rules`: Artifact-specific rules (constraints for you - do NOT include in output)63 - `template`: The structure to use for your output file64 - `instruction`: Schema-specific guidance65 - `resolvedOutputPath`: Resolved path or pattern to write the artifact66 - `dependencies`: Completed artifacts to read for context67 - **Create the artifact file**:68 - Read any completed dependency files for context69 - Use `template` as the structure - fill in its sections70 - Apply `context` and `rules` as constraints when writing - but do NOT copy them into the file71 - Write to the `resolvedOutputPath` specified in instructions. If it is a glob pattern, choose the concrete file path using the schema instruction and workspace planning context72 - Show what was created and what's now unlocked73 - STOP after creating ONE artifact7475 ---7677 **If no artifacts are ready (all blocked)**:78 - This shouldn't happen with a valid schema79 - Show status and suggest checking for issues80814. **After creating an artifact, show progress**82 ```bash83 openspec status --change "<name>"84 ```8586**Output**8788After each invocation, show:89- Which artifact was created90- Schema workflow being used91- Current progress (N/M complete)92- What artifacts are now unlocked93- Prompt: "Want to continue? Just ask me to continue or tell me what to do next."9495**Artifact Creation Guidelines**9697The artifact types and their purpose depend on the schema. Use the `instruction` field from the instructions output to understand what to create.9899Common artifact patterns:100101**spec-driven schema** (proposal → specs → design → tasks):102- **proposal.md**: Ask user about the change if not clear. Fill in Why, What Changes, Capabilities, Impact.103 - The Capabilities section is critical - each capability listed will need a spec file.104- **specs/<capability>/spec.md**: Create one spec per capability listed in the proposal's Capabilities section (use the capability name, not the change name).105- **design.md**: Document technical decisions, architecture, and implementation approach.106- **tasks.md**: Break down implementation into checkboxed tasks.107108For other schemas, follow the `instruction` field from the CLI output.109110**Guardrails**111- Create ONE artifact per invocation112- Always read dependency artifacts before creating a new one113- Never skip artifacts or create out of order114- If context is unclear, ask the user before creating115- Verify the artifact file exists after writing before marking progress116- Use the schema's artifact sequence, don't assume specific artifact names117- **IMPORTANT**: `context` and `rules` are constraints for YOU, not content for the file118 - Do NOT copy `<context>`, `<rules>`, `<project_context>` blocks into the artifact119 - These guide what you write, but should never appear in the output