openspec-ff-change

To generate all OpenSpec change artifacts at once, use an automated scaffolding workflow that parses status JSON and creates spec, task, and implementation files in dependency order. This fast-forwards a change to apply-ready status without manually running each CLI command.

The best way to scaffold OpenSpec change artifacts is by using a dependency-driven workflow that parses status and instructions JSON. It reads completed dependencies for context, iterates through required artifacts, and populates them in the correct sequence to reach apply-ready status.

Yes, you can automate OpenSpec CLI workflows to eliminate repeated status checks. By orchestrating CLI commands and parsing JSON instructions, the system iterates through artifact generation until all dependencies are satisfied, removing the need to manually step through each status update.

OpenSpec change generation only prompts you when context is ambiguous during artifact creation. It operates autonomously through dependency resolution and file generation, asking for user clarification solely when needed, then reports progress with confirmations and a final readiness summary.

To start creating OpenSpec artifacts for a new feature, you need to provide a change name or description of what you want to build. The scaffolding process then automatically orchestrates the CLI commands to populate tasks, specs, and other required artifacts.

Your OpenSpec change workflow requires manual steps because it lacks automated scaffolding. Implementing a dependency-driven generator parses JSON status instructions, creates files from templates, and handles artifact dependencies automatically to fast-forward the change to apply-ready state.