openspec-ff-change

Generates all OpenSpec change artifacts in one fast-forward workflow.

4|Updated May 13, 2026
One-click install
npx skills add https://github.com/RuixeWolf/modbus-simulator --skill openspec-ff-change-ruixewolf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/RuixeWolf/modbus-simulator/tree/main/.opencode/skills/openspec-ff-change
Command: npx skills add https://github.com/RuixeWolf/modbus-simulator --skill openspec-ff-change-ruixewolf

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 for implementation in a single workflow. ## Core Features & Use Cases - Batch Artifact Creation: Derives the full required artifact set from openspec status --json by transitively following dependency edges, then creates each one in order. - Store-Aware Operation: Discovers registered OpenSpec stores via openspec store list --json and applies a sticky --store <id> flag to all scoped commands. - Dependency-Aware Generation: Reads completed dependency artifacts from disk before drafting each new artifact, and respects conditional or skipped artifacts declared in .openspec.yaml. - Use Case: You describe a feature like "add user authentication" and the Skill scaffolds the change, generates the proposal, specs, design, and tasks files, then reports that everything is ready for implementation. ## Quick Start Ask the assistant to fast-forward an OpenSpec change named add-user-auth so all implementation artifacts are created at once.

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 workflow with a change name or description. It calls openspec new change, reads the dependency graph from openspec status --json, and generates every artifact required for implementation in dependency order.

How does OpenSpec determine which artifacts a change needs?▼

The openspec status --json output lists applyRequires plus each artifact's requires edges. The required set is built by transitively following those edges, since a done status only means the file exists, not that its dependencies were created.

Does the openspec fast-forward workflow support multiple stores?▼

Yes. It runs openspec store list --json to discover registered store ids, then appends --store <id> to every command that reads or writes specs and changes. Without a store, commands act on the nearest local openspec directory.

When are OpenSpec artifacts skipped during change creation?▼

An artifact is skipped only when status reports it as skipped due to skip_specs in .openspec.yaml, or when its own instruction field marks it conditional, such as design.md in the spec-driven schema. Blocked artifacts with skipped conditional dependencies are still written.

What are the requirements for running the OpenSpec fast-forward skill?▼

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.