openspec-continue-change

You can create the next OpenSpec artifact by using a workflow automation Skill that runs openspec CLI status checks, reads schema-specific instructions, and generates the pending proposal, specs, design, or tasks files in sequence.

Spec-driven change management is a workflow where project modifications require sequential artifacts like proposals, specs, and designs. Tools like openspec CLI enforce this by tracking artifact status and providing schema-specific instructions for creating each required file.

To know which OpenSpec artifact to write next, run the openspec status command. It inspects the change's current state and identifies the first artifact marked as ready, ensuring you follow the correct dependency-aware sequence for your project files.

Yes, you need the openspec CLI installed on your system. The automation requires running openspec list, status, and instructions commands to identify the change, check pending artifacts, and read the templates needed for dependency-aware writing.

Yes, you can generate spec files from an existing proposal. The automation reads the completed proposal artifact for context, applies the openspec instructions and schema templates, and enforces the specified rules to produce the corresponding spec or design artifact.

Limitations include requiring the openspec CLI on the system and needing explicit read and write permissions for project artifact files. The automation only creates artifacts marked as ready by the CLI status check and cannot skip the required dependency sequence.