openspec-continue-change

Automating OpenSpec change continuation requires reading completed artifacts, assessing status, and generating the next artifact in sequence. This skill enforces the required workflow by checking dependencies and prompting for a change name when context is ambiguous.

Dependency-aware artifact creation works by reading completed artifacts and checking their status to determine readiness. It enforces the proper workflow sequence, ensuring the next artifact is only created when dependencies are respected and the change is ready to progress.

Yes, you can use CLI instructions to control OpenSpec change continuation. The skill respects CLI-provided instructions and constraints, writes artifacts to specified output paths, and prompts for user input only when the change selection is ambiguous.

The best way to track and continue an OpenSpec change is using status-driven progress. By running an openspec status check, you can identify which artifacts are ready for creation or determine if the change is fully complete before generating the next file.

The OpenSpec workflow prompts you to select a change name when the context is ambiguous. It requires explicit user selection before proceeding to ensure the next artifact is created for the correct change and dependencies are properly tracked.

No, you do not need to manually check artifact status. The continuation process automatically uses status assessment to identify when artifacts are ready for creation or when the change is complete, handling dependencies without manual intervention.