openspec-continue-change

To automate OpenSpec change management, this Skill advances your current change by validating its status and generating the next required artifact in the correct sequence. It enforces single-artifact creation per invocation to maintain orderly progression.

Continuously progressing a spec-driven development workflow requires orchestrating artifact generation from proposal to implementation. This Skill determines the active change, checks dependencies, and creates the next artifact according to the schema.

Dependency validation for OpenSpec artifacts works by enforcing guardrails that check completed artifacts before writing new ones. The Skill ensures single-artifact-per-invocation creation and verifies dependency awareness to maintain correct schema ordering.

Yes, you can use this CLI automation tool with both spec-driven and TDD schemas. It extends changes from proposal to implementation to docs as needed, adapting artifact generation to the specific workflow schema you are using.

Your OpenSpec workflow stops after creating one artifact because the Skill enforces single-artifact-per-invocation guardrails. You must invoke the Skill again to read the completed artifact, validate dependencies, and generate the next sequential artifact.

You do not need to manually specify which OpenSpec change to work on. If a change is not specified, the Skill will prompt you to choose one before validating its status and generating the next artifact.