openspec-ff-change

To generate OpenSpec artifacts automatically, provide a change name or description to trigger automated scaffolding, which creates the change directory and outputs all required task, spec, and implementation files in dependency order. The process stops when apply-ready requirements are met.

Scaffolding a change directory with the openspec CLI is best achieved by providing a kebab-case change name, allowing the workflow to resolve dependencies and generate implementation artifacts sequentially until the apply-ready state is reached.

Yes, you need the openspec CLI installed and filesystem access to the repository change directory. The workflow relies on running openspec commands to read and write artifact files required for apply-ready generation.

Yes, when input is unclear, an interactive clarification prompt appears to derive a valid kebab-case change name and validate your intent before creating the OpenSpec implementation files.

Automated artifact generation stops once apply-requirements are satisfied because the workflow uses a progress tracker to monitor completed artifacts, ensuring the change is apply-ready without creating unnecessary files.

You track progress using a todo-style tracker that displays completed artifacts during the scaffolding workflow, ensuring visibility into dependency resolution until all apply-required OpenSpec artifacts are generated.