openspec-ff-change

Generates all OpenSpec change artifacts in one pass using the openspec CLI.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/germainlefebvre4/cvwonder-forms --skill openspec-ff-change-germainlefebvre4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/germainlefebvre4/cvwonder-forms/tree/main/.gemini/skills/openspec-ff-change
Command: npx skills add https://github.com/germainlefebvre4/cvwonder-forms --skill openspec-ff-change-germainlefebvre4

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 run. ## 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. - Dependency-Aware Ordering: Reads completed dependency artifacts from disk before writing new ones, and respects skipped and conditional artifacts declared via skip_specs. - Store-Aware Operation: Detects named OpenSpec stores via openspec store list --json and passes --store <id> to all relevant commands. - Use Case: A developer describes a feature like "add user authentication"; the Skill derives the kebab-case name add-user-auth, scaffolds the change, and produces the proposal, specs, design, and tasks files ready for implementation. ## Quick Start Ask the assistant to fast-forward an OpenSpec change by describing what you want to build, for example: create all artifacts for a change that adds user authentication.

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?

Provide a change name or a description of what you want to build, and the Skill runs openspec new change, then loops through the required artifacts in dependency order using openspec status and openspec instructions until every required file exists.

How does the Skill decide which OpenSpec artifacts to create?

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 rather than relying on file-existence status alone.

Does this work with named OpenSpec stores?

Yes. If the user names a store, the Skill runs openspec store list --json to find registered store ids and passes --store <id> to commands that read or write specs and changes.

What happens when an artifact is marked skipped or conditional?

Artifacts with status skipped (from skip_specs in .openspec.yaml) are never created. Conditional artifacts like design.md are skipped only when their own instruction field marks them optional, and the user is told why.

What are the requirements for using this OpenSpec fast-forward workflow?

The openspec CLI must be installed and available in the environment. The Skill only invokes openspec commands and writes artifact files to the resolved paths returned by the CLI.