openspec-continue-change

To continue an OpenSpec change, the workflow automates next artifact generation by inferring the step, checking status, reading dependencies, and applying schema-guided templates. Invoking the process creates exactly one artifact file per run while respecting dependency-aware writing constraints.

Artifact sequencing in OpenSpec change management dictates the progressive creation of workflow files. The automation reads current status and dependencies to infer the correct next artifact, applying schema-aware templates to ensure structured, sequential progression throughout the change lifecycle.

Yes, OpenSpec workflow automation supports both spec-driven and alternative workflows. It coordinates task creation with progress tracking, ensuring that generating the next artifact aligns with your chosen workflow methodology and maintains accurate lifecycle reporting.

Template application and dependency constraints work by applying schema-aware templates to produce the next artifact file. The process reads existing dependencies and context rules, ensuring dependency-aware writing and enforcing guardrails like one artifact per invocation.

Limitations of automating OpenSpec change progression include a strict guardrail of generating only one artifact per invocation. Additionally, the automation relies on accurate status inspection and dependency reading, meaning incomplete context or missing schema guidance can halt the workflow progression.