openspec-ff-change

Automate OpenSpec change artifact generation by running `openspec new change "<name>"` to scaffold the change directory with all required artifacts in dependency order, then use `openspec status --change "<name>" --json` to verify completion. This eliminates manual file creation and setup work.

OpenSpec change management automatically generates all required artifact files under openspec/changes/<name> based on dependency analysis and instruction schemas. The Skill orchestrates creation in dependency order so implementation can begin immediately after scaffolding completes.

Yes. The OpenSpec CLI-driven workflow automates rapid scaffolding of change artifacts by reading dependency artifacts and applying instruction schemas. This speeds feature requests from idea to ready-to-implement artifacts without manual template work.

OpenSpec reads dependency artifacts and generates templates in dependency order, ensuring all required files are created in the correct sequence. Query status with `--json` to track completion and verify that all artifacts respect declared dependencies.

Stage changes via `openspec new change "<name>"`, verify readiness with `openspec status --change "<name>" --json`, then implementation proceeds in dependency order. This Skill automates the scaffolding phase so staged changes apply consistently across the repository.

You need the openspec CLI available and an openspec/changes directory structure in your repository. The Skill automates artifact creation within that environment; no manual scaffolding or template editing is required before you run `openspec new change`.