openspec-ff-change

To generate OpenSpec artifacts in one pass, provide a kebab-case change name and the Skill reads the dependency-ordered build instructions from the openspec CLI, writing all required scaffolding files until the change is apply-ready.

Automating OpenSpec change scaffolding involves using the openspec CLI to fetch JSON status and instructions, then automatically writing template-driven artifacts to their required output paths based on dependency resolution.

No, you do not need to manually step through OpenSpec artifact creation. This Skill fast-forwards through template-driven generation, reading applyRequires conditions and stopping only when all dependency-ordered artifacts are marked done.

Yes, you can use openspec CLI instructions to generate implementation files automatically. The Skill reads template schemas from the instructions JSON and writes outputs directly to required paths without manual intervention.

Dependency resolution matters because OpenSpec artifacts require a specific build order. The Skill reads this order from openspec status --json to ensure each artifact respects context and schema instructions before marking the change apply-ready.

Yes, automated artifact generation works for both feature and fix planning workflows. It scaffolds the change directory and generates all required implementation artifacts immediately for either workflow context.