openspec-ff-change

Generates all OpenSpec change artifacts in dependency order for implementation readiness.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/GQAdonis/artifact-refiner-skill --skill openspec-ff-change-gqadonis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/GQAdonis/artifact-refiner-skill/tree/main/.kimi-code/skills/openspec-ff-change
Command: npx skills add https://github.com/GQAdonis/artifact-refiner-skill --skill openspec-ff-change-gqadonis

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 workflow. ## Core Features & Use Cases - Batch Artifact Creation: Derives the full required artifact set from openspec status JSON, including transitive dependencies, and creates each one in dependency order. - Instruction-Driven Generation: Reads per-artifact templates, rules, and context from openspec instructions so each file follows the correct schema. - Store-Aware Operation: Supports named OpenSpec stores via --store <id> flags discovered through openspec store list --json. - Use Case: A developer describes a new feature like "add user authentication"; the Skill creates the change scaffold, then writes the proposal, specs, design, and tasks files so implementation can begin immediately. ## Quick Start Ask the assistant to fast-forward an OpenSpec change by describing what you want to build, for example requesting it to create all artifacts for adding 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?

Invoke the fast-forward workflow with a change name or a description of what you want to build. It runs openspec new change, reads the dependency graph from openspec status, and creates every required artifact in order.

How does OpenSpec determine which artifacts are required?

The required set comes from the applyRequires field plus every artifact reachable by following requires edges in the openspec status JSON output. Status alone is file-existence based, so dependency edges define the true required set.

Does the openspec fast-forward skill require the openspec CLI?

Yes, the openspec CLI must be installed since the workflow runs commands like openspec new change, status, and instructions. Without the CLI, artifact scaffolding and dependency resolution cannot run.

Can I use OpenSpec changes with a named store?

Yes, run openspec store list --json to discover registered store ids, then pass --store <id> on commands that read or write specs and changes. The flag stays sticky for the rest of the workflow.

When should an OpenSpec artifact be skipped during creation?

Skip an artifact only when its status reports skipped due to skip_specs in .openspec.yaml, or when its own instruction field marks it conditional, such as design.md. Never skip specs based on your own judgment.