openspec-continue-change

To automate OpenSpec artifact creation, this skill parses JSON status outputs and orchestrates the generation of sequential artifacts, enforcing schema-specific constraints to ensure dependencies are met and artifacts are created in the correct sequence.

Enforcing schema-driven workflow dependencies is achieved by parsing project status outputs and applying schema-specific constraints, which prevents skipped steps or out-of-order development during complex software engineering tasks.

Yes, you need the openspec CLI installed and configured within your project environment to execute status checks and generate the next required artifact based on the current schema.

Context-aware progression identifies the next required document by parsing the current JSON status output and evaluating it against the project schema, automatically generating files like design documents or task lists based on previously completed specs.

Your OpenSpec workflow fails because this skill enforces workflow dependencies and schema-specific constraints, actively preventing the creation of out-of-order artifacts to ensure sequential development changes are managed correctly.

Yes, you can use this skill to automatically generate downstream task lists and design files from completed proposals and capability specs by parsing the current project status to identify pending artifacts.