openspec-ff-change

To scaffold OpenSpec change artifacts, provide a change name or description and the automation iteratively creates and validates all apply-required files in dependency order until implementation prerequisites are complete.

The OpenSpec change workflow process queries openspec status and instructions, reads completed dependencies for context, and follows templates and schema rules to iteratively generate every required artifact.

Yes, you need the openspec CLI available and the ability to run openspec status and openspec instructions to parse JSON output for dependency-aware artifact generation and validation.

Dependency-aware execution queries openspec status and instructions, reads completed dependency artifacts for context, and follows schema rules and templates to write files in the correct dependency order.

When input is unclear during artifact generation, the automation asks interactive clarifying questions and records progress using a TodoWrite-style tracker to ensure all required artifacts are correctly created.

Yes, you can rehydrate stalled OpenSpec change scaffolds by providing the change name, and the automation will check artifact status and resume iterative creation of any remaining apply-required artifacts.