openspec-continue-change

To continue an OpenSpec workflow, the skill checks current artifact status via the CLI, identifies the next eligible artifact, and fetches its instructions to guide creation. It reads completed dependency artifacts first to preserve context and ensure correct sequencing.

Dependency-aware artifact creation works by reading completed artifacts before generating a new one. This preserves context and ensures the new artifact adheres to schema-driven generation rules, retrieving necessary instructions and dependencies before writing to the designated path.

You cannot skip artifact steps. The skill enforces correct sequencing by applying order constraints, preventing skipping artifacts, and ensuring each artifact unlocks in the proper order based on dependency status retrieved from the CLI.

You need the OpenSpec CLI to automate change continuation. The skill uses the CLI to check the current artifact status, retrieve artifact instructions, and determine the next eligible artifact before writing the new artifact to the designated path.

The best way to manage artifact sequencing is using a schema-driven approach that reads dependency artifacts before creation. This prevents skipping steps, enforces correct unlocking order, and writes new artifacts to designated paths based on CLI status checks.

Workflow artifact creation fails because the skill requires reading completed dependency artifacts before creating a new one. This dependency-aware mechanism preserves context and enforces correct sequencing to avoid skipping steps in the OpenSpec workflow.