openspec-ff-change

Automating OpenSpec artifact generation involves using a CLI to scaffold a change directory, enumerate required artifacts, and iterate file creation in dependency order until apply-ready. This eliminates manual step-by-step artifact creation and dependency churn.

Resolving artifact dependencies requires fetching per-artifact instructions, reading completed dependency files for context, and writing new files from templates iteratively. This ensures all required artifacts are produced in the correct dependency order before applying a change.

Yes, creating change artifacts requires OpenSpec CLI interactions to query status, fetch instructions, and create files from templates. The CLI provides the necessary commands to enumerate required artifacts and track progress until the change is apply-ready.

Start fast-forward creation by providing a kebab-case name or short description like add-user-auth. The automation tool scaffolds the change directory, enumerates artifacts via status, and iterates through dependency-ordered file generation until complete.

Progress tracking during OpenSpec artifact generation uses a TodoWrite-style tool to monitor the iterative creation process. The system surfaces a final status summary upon completion, enabling you to trigger subsequent implementation or apply steps.

OpenSpec artifact creation integrates lightweight user prompts when context is unclear during the dependency resolution and file generation process. This ensures artifacts are accurately populated before proceeding to the next dependency in the iteration.