openspec-ff-change

Generates all required OpenSpec change artifacts in one dependency-ordered pass.

5|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/8007342/tillandsias --skill openspec-ff-change-8007342
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/8007342/tillandsias/tree/main/.opencode/skills/openspec-ff-change
Command: npx skills add https://github.com/8007342/tillandsias --skill openspec-ff-change-8007342

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, resolving dependencies automatically. ## Core Features & Use Cases - Batch Artifact Creation: Derives the full required artifact set from openspec status --json by transitively walking requires edges, then creates each artifact in dependency order. - Schema-Driven Output: Pulls per-artifact templates, rules, and instructions via openspec instructions so every file follows the correct schema without manual lookup. - Store-Aware Operation: Supports registered OpenSpec stores by discovering store ids with openspec store list --json and applying --store <id> consistently across commands. - Use Case: A developer describes "add user authentication" and receives a complete change folder with proposal, specs, design, and tasks files ready for implementation, without running each creation step interactively. ## 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 workflow with a change name or description. It calls openspec new change, reads the dependency graph from openspec status --json, and creates each required artifact in order using the templates from openspec instructions.

What is the difference between fast-forward and step-by-step OpenSpec artifact creation?▼

Step-by-step creation walks through each artifact interactively, while fast-forward generates the entire required set in one pass. Fast-forward still follows each artifact's schema and instructions, but only asks for input when context is critically unclear.

Does openspec-ff-change require the openspec CLI?▼

Yes, the openspec CLI must be installed and available. The Skill runs commands like openspec new change, status, and instructions, and its frontmatter declares compatibility requiring the CLI.

Can I use OpenSpec fast-forward with a registered store?▼

Yes. If the work lives in a registered store, the Skill discovers store ids with openspec store list --json and appends --store <id> to all commands that read or write specs and changes for the rest of the workflow.

Why does the workflow create artifacts not listed in applyRequires?▼

The required set is applyRequires plus every artifact reachable by following requires edges transitively. Status only reflects file existence, so a done artifact can still have missing dependencies that must be created first.