openspec-continue-change

To generate the next OpenSpec artifact, the skill checks the current change status and automatically creates the required proposal, spec, design, or task file based on the defined schema instructions. It uses the OpenSpec CLI to determine which artifact is next in the sequence.

The OpenSpec workflow sequence progresses through specific artifacts like proposals, specs, designs, and tasks. This skill automates progression by checking artifact status and generating the next required file, ensuring your development workflow adheres to the defined schema.

Yes, the OpenSpec CLI is required to generate specification files. The skill relies on the CLI to list available changes, check artifact status, and execute the generation of specific workflow files based on schema instructions.

You can select a specific OpenSpec change by providing its name in conversation context, or the skill will prompt you using the `openspec list` command. It infers the target change to generate the next artifact like a spec or design file.

Yes, you can automatically create a specification file after a proposal. The skill tracks artifact status and proceeds with the next available item, generating the corresponding spec file based on the capabilities listed in your completed proposal.

Automation is limited to generating artifacts defined within the OpenSpec schema sequence. It requires the CLI for status checks and cannot create files outside the specified proposal, spec, design, or task workflow structure.