openspec-ff-change

Generates all OpenSpec change artifacts in dependency order via the openspec CLI.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill openspec-ff-change-codercoco-studios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/CoderCoco-Studios/Hyveon/tree/main/.claude/skills/openspec-ff-change
Command: npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill openspec-ff-change-codercoco-studios

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating an OpenSpec change normally requires stepping through each artifact (proposal, specs, design, tasks) one at a time. This Skill fast-forwards the process by generating every artifact needed before implementation in a single pass, resolving dependencies automatically. ## Core Features & Use Cases - Batch artifact creation: Runs openspec new change, then walks the dependency graph from openspec status --json to create every artifact the apply phase transitively requires. - Instruction-driven generation: Fetches per-artifact templates, rules, and context via openspec instructions, and delegates to other skills or commands when the instruction field says so. - Store-aware operation: Supports named OpenSpec stores via openspec store list --json and the --store <id> flag on relevant commands. - Use Case: You describe "add user authentication" and the Skill creates the change add-user-auth, then produces the proposal, specs, design, and tasks files in order, ending with a status summary ready for implementation. ## Quick Start Ask the assistant to fast-forward an OpenSpec change, for example: create all artifacts for a change named add-user-auth so I can start implementation.

Frequently Asked Questions about openspec-ff-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create all OpenSpec change artifacts at once?

Run the fast-forward flow: it calls openspec new change with a kebab-case name, reads the dependency graph from openspec status --json, and creates each required artifact using the template from openspec instructions until the apply set is complete.

How do I use OpenSpec with a named store instead of a local repo?

Run openspec store list --json to discover registered store ids, then pass --store <id> on commands that read or write specs and changes such as new change, status, instructions, list, show, validate, and archive.

Does the openspec CLI need to be installed for this workflow?

Yes, the workflow requires the openspec CLI because every step shells out to commands like openspec new change, openspec status, and openspec instructions. Without the CLI installed, artifact scaffolding and status checks cannot run.

Why is an OpenSpec artifact marked skipped or left uncreated?

An artifact reads skipped when the change declares skip_specs in .openspec.yaml, meaning its files must not exist. Conditional artifacts like design.md may also be skipped when their own instruction field marks them optional.

What happens if a change with the same name already exists?

The workflow suggests continuing the existing change instead of creating a duplicate. You can then re-run status and instructions against that change name to resume artifact creation where it left off.