openspec-continue-change

To generate the next artifact in an OpenSpec change workflow, use this Skill to check the change status and automatically create the required file, such as a proposal, specification, or task list.

Automated artifact generation for spec-driven development works by inferring the current change state, retrieving instructions via the OpenSpec CLI, and producing the next sequential document using predefined schema templates.

Yes, you need the OpenSpec CLI installed to automate change management artifact creation, as the Skill depends on it to perform status checks and retrieve the necessary generation instructions.

Yes, you can automatically create a specification from an existing OpenSpec proposal by running this Skill, which identifies the completed proposal and generates the matching specification artifact for the specified capability.

The best way to progress a spec-driven development sequence is to use this Skill to automate workflow continuation, ensuring each artifact from proposal to task list is generated in the correct predefined order.

Your OpenSpec change workflow stops progressing between artifacts when the next file in the schema sequence is missing; this Skill resolves the block by automatically generating the required subsequent artifact.