openspec-continue-change

To generate the next artifact for an OpenSpec change, the workflow programmatically determines the required file—such as a proposal, spec, design, or task—and creates it based on project status and schema definitions via the acfm CLI.

Spec-driven development artifact generation is the process of sequentially creating required workflow files like proposals and specifications. It ensures development progress and adherence to predefined project schemas.

Yes, you need the acfm CLI to generate OpenSpec specifications. The CLI is required to perform status checks, retrieve artifact instructions, and programmatically generate the sequential workflow files.

To continue work on an existing OpenSpec proposal, the workflow infers the current change from your conversation or prompts you for selection, then automatically creates the corresponding specification file based on the proposal's capabilities.

The best way to manage sequential workflow files in spec-driven development is to use an automated progression system that determines the next required artifact from project status and generates it according to schema requirements, ensuring consistent adherence to specifications.

OpenSpec workflow artifact generation stops after the proposal if the predefined schema requirements for the next sequential file are not met, or if the acfm CLI cannot retrieve the correct status checks and artifact instructions to proceed.