openspec-ff-change

Automate OpenSpec change artifact creation by using a fast-forward workflow that generates all required artifacts in dependency order. It queries openspec status and instructions, parsing JSON outputs to iteratively scaffold files until all applyRequires entries are complete.

Scaffolding OpenSpec changes without manual steps involves executing openspec new commands to create a change directory, then iteratively reading dependency artifacts and verifying status. This enforces dependency order and prevents missing required implementation files.

Yes, fast-forwarding change artifact generation requires the openspec CLI to run new, status, and instructions commands. File system access to the openspec/changes/<name> directory is also necessary to read and verify the generated artifacts.

You can track progress when generating OpenSpec change artifacts using a TodoWrite tool during the iterative creation workflow. It also interactively prompts the user for clarification when input is unclear, ensuring implementation-ready specifications.

OpenSpec artifact generation requires an iterative workflow because artifacts have dependencies that must be resolved in order. By repeatedly querying openspec status, parsing JSON, and reading dependency artifacts, it ensures nothing required for apply is missed.

Use fast-forward artifact creation for OpenSpec changes when moving from specification to implementation in OpenSpec-managed repositories. It removes repetitive scaffolding work for product managers and engineers preparing implementation-ready specs.