openspec-continue-change

To continue an OpenSpec change, this Skill programmatically generates the next required artifact, such as a proposal, specification, design, or tasks, based on your current workflow stage. It identifies the next actionable step and provides the necessary context and instructions.

Spec-driven development artifact generation works by querying the OpenSpec CLI for status checks and retrieving artifact instructions. It then automatically creates the next file, like a specification for a capability defined in a proposal, to ensure process adherence.

Yes, you need the OpenSpec CLI installed to generate specifications and tasks. The Skill depends on the CLI to perform status checks and retrieve the necessary instructions for creating the next artifact in your predefined workflow.

The best way to manage a spec-driven workflow is to automate the progression between stages. This Skill identifies the next actionable step after a proposal and automatically generates the corresponding specification, design, or tasks file to maintain momentum.

Yes, you can automatically create a specification file after writing an OpenSpec proposal. Once the proposal is complete, the Skill identifies the corresponding capability and generates the required specification artifact to progress the change.

Your OpenSpec workflow may stall if the next artifact instructions are not retrieved. This Skill checks the current status via the CLI and programmatically generates the required design document or tasks to ensure continuous progress.