openspec-continue-change

To advance an OpenSpec change, the skill parses CLI status and instruction JSON, reads dependency files, fills templates, and writes the next artifact file to the specified output path. It enforces schema order and creates exactly one artifact per invocation.

When the change name is ambiguous or not provided, the skill lists recent changes, highlights a recommended choice, and prompts the user to select one. This guided selection ensures you target the correct workflow before generating artifacts.

No, the skill enforces strict guardrails by creating exactly one artifact per invocation. This schema-driven approach ensures dependency checks are satisfied and template rules are followed for each specific artifact before moving forward.

No, the skill handles CLI orchestration internally by calling openspec status and instructions, parsing JSON outputs, and reading completed dependencies automatically. This removes the need to manually run multiple commands and interpret JSON.

The change workflow follows template and rule constraints by parsing instruction JSON, verifying completed dependency files, and strictly enforcing schema order. If context is ambiguous, it prompts the user for clarification before writing the artifact.