openspec-continue-change

You can generate the next artifact by prompting the AI to continue the OpenSpec change. The skill reads the current change status, selects the appropriate ready artifact, fetches its specific instructions, and writes the output to the configured path.

The best way to advance an OpenSpec change is to use an automated workflow tool that enforces guardrails and dependency order. This skill determines the next required artifact based on status and ensures all project constraints are honored during generation.

Status-driven artifact generation works by reading the current OpenSpec change status to determine which artifact is ready next. It then fetches the necessary instructions for that specific artifact and writes the file to the specified output location.

Yes, the workflow honors configured output paths when writing artifacts. It enforces dependency order and respects project constraints, ensuring the generated artifact is placed in the specified output location defined by your configuration.

Yes, this skill enforces the OpenSpec CLI flow to continue changes. It relies on the CLI to read the current status, select a ready artifact, fetch its instructions, and write the artifact to the output, ensuring a smooth continuation of the workflow.

Your OpenSpec change workflow may fail if dependency order is not honored or if project constraints block progression. This skill enforces guardrails and reads the active status to ensure the next required artifact is only generated when dependencies are met.