openspec-continue-change

To generate the next artifact in an OpenSpec change workflow, you need a tool that checks your current status via the openspec CLI and automatically creates the next required document in the correct sequence.

Artifact generation in spec-driven workflows is the process of automatically creating required documents like proposals, specs, designs, and tasks in a defined sequence, ensuring correct creation order and managing dependencies.

Yes, you need the openspec CLI installed to automate specification generation, as the workflow relies on the CLI for performing status checks, retrieving instructions, and executing the actual artifact generation.

Dependency management when creating specification documents ensures artifacts are generated in the correct order by respecting schema rules, verifying existing artifacts and dependencies before creating the next sequential document.

Yes, you can automatically create a specification from an existing proposal by continuing the change workflow, where the system infers the current change context and generates the corresponding specification based on the proposal's capabilities.

A key limitation of automating OpenSpec workflow progression is the strict requirement for the openspec CLI for status checks and generation, while artifact creation is bound by schema rules and dependencies, preventing out-of-order document generation.