openspec-ff-change

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

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/JhonMA82/api-starter --skill openspec-ff-change-jhonma82
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/JhonMA82/api-starter/tree/main/.opencode/skills/openspec-ff-change
Command: npx skills add https://github.com/JhonMA82/api-starter --skill openspec-ff-change-jhonma82

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 walking requires edges transitively, then creates each one in dependency order. - Instruction-Driven Generation: Pulls per-artifact templates, rules, and context via openspec instructions and delegates to specific skills or commands when the schema requires it. - Store-Aware Operation: Supports named OpenSpec stores via openspec store list --json and applies --store <id> consistently across all commands. - Use Case: You describe "add user authentication" and the Skill creates the change scaffold, then writes the proposal, specs, design, and tasks files so you can immediately run /opsx-apply to start implementation. ## Quick Start Ask the assistant to fast-forward an OpenSpec change named add-user-auth so all planning artifacts are generated 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 required artifact in order using each artifact's instructions and template.

How does OpenSpec determine which artifacts are required before implementation?▼

The required set comes from the applyRequires field plus every artifact reachable by following requires edges transitively in the status JSON. File-existence status alone is not trusted, since a done artifact can still list unmet dependencies.

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

Yes. Run openspec store list --json to discover registered store ids, then pass --store <id> on commands like new change, status, instructions, and validate. The flag stays sticky for the rest of the workflow.

What happens when an OpenSpec artifact is marked skipped?▼

An artifact with status skipped means the change declares skip_specs in .openspec.yaml, so its files must not exist. The workflow never creates skipped artifacts and treats them as already satisfied.

Why does OpenSpec status show tasks done but specs missing?▼

Status is file-existence only, so writing tasks.md early marks tasks done even if specs was never written. Always build the required set from each artifact's requires edges rather than its reported status.