openspec-ff-change

Run the fast-forward workflow: it calls openspec new change to scaffold the change, reads openspec status --json for the dependency graph, then creates each required artifact in order using openspec instructions. You only provide a change name or a description of what to build.

It parses the applyRequires array and each artifact's requires edges from openspec status --json, then walks those edges transitively to build the full required set. Artifacts marked skipped or conditionally optional per their instruction field are left out.

Yes. If the user names a store, it runs openspec store list --json to find the store id, then appends --store <id> to every scoped command such as new change, status, instructions, and validate. Without a store, commands act on the nearest local openspec root.

An artifact with status skipped means the change declares skip_specs in .openspec.yaml, so its files must not exist. The skill treats it as satisfied, never attempts to create it, and continues with the remaining required artifacts.

You need the openspec CLI installed and either a local openspec directory or a registered store. You also provide a kebab-case change name or a description of what you want to build so the skill can derive one.