openspec-ff-change

OpenSpec change artifacts are the tasks, specs, and docs files required before implementation begins. Generating them in dependency order ensures all templates and apply-require checks are satisfied sequentially without manual scaffolding errors.

To scaffold an OpenSpec change directory, the automation queries openspec status and instructions JSON outputs to determine artifact templates and order, re-checking status after each artifact is created until the entire set is apply-ready.

Yes, the openspec CLI is required to automate change artifact generation. The workflow relies on openspec status and openspec instructions JSON outputs to determine artifact order, templates, and apply-require checks throughout the scaffolding process.

The best way to avoid manual scaffolding errors is using end-to-end artifact generation that applies dependency-aware workflow logic. It queries openspec CLI outputs to resolve dependencies and templates, re-checking status after each artifact creation step.

Yes, interactive clarification is supported during OpenSpec change artifact generation. The workflow prompts the user when input is unclear and records progress using a TodoWrite-style tracker to ensure all required artifacts are created correctly.