openspec-continue-change

Automate artifact sequencing by identifying the target OpenSpec change, querying its current status, and deriving the next artifact from dependencies. The workflow reads completed artifacts to ensure creation order and writes the new artifact to its designated path using the openspec CLI.

Dependency-aware artifact creation works by reading any completed artifacts within the OpenSpec change to determine prerequisites. It then applies the current workflow template to generate the next artifact consistently, ensuring all dependencies are resolved before writing the new file to its path.

Yes, you can use the openspec CLI to query the current status of an OpenSpec change. The workflow uses this status check to identify which dependencies are completed and derives the next artifact directly from the designated template.

The best way to advance an OpenSpec change is through a status-driven workflow that identifies the target change and applies the current template. It progresses the change by reading completed dependencies and writing the next required artifact in the sequence.

Your OpenSpec change workflow requires completed dependencies to ensure artifacts are created in the correct sequence. Reading completed dependencies allows the workflow to derive the next artifact accurately from the template and maintain consistency throughout the change management process.

Yes, the openspec-continue-change Skill guides users through change selection, status checks, and artifact creation. It initiates the creation of the next artifact by applying the current workflow and writing the output to its designated path within the OpenSpec change.