What problem does it solve? When working through an OpenSpec change workflow, it is hard to know which artifact (proposal, specs, design, tasks) comes next and how to generate it correctly. This Skill inspects the change status and creates exactly one ready artifact per invocation. ## Core Features & Use Cases - Status-driven artifact creation: Runs openspec status to determine which artifact is ready, then fetches its instructions and writes the file to the correct output path. - Change selection: Lists recent changes via openspec list --json and prompts the user to pick one when no change name is given. - Context loading: Silently loads context briefs, ADRs, and architecture docs so generated artifacts respect project constraints. - Use Case: After finishing a proposal for a new feature, run the Skill to generate the capability specs, then the design document with seed data, then the task breakdown — one artifact at a time. ## Quick Start Ask the assistant to continue working on your change by running /opsx-continue with an optional change name such as add-webhook-support.
