openspec-ff-change

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

1|1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/phuchoang2603/nixos --skill openspec-ff-change-phuchoang2603
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/phuchoang2603/nixos/tree/main/home/base/cli/skills/openspec-ff-change
Command: npx skills add https://github.com/phuchoang2603/nixos --skill openspec-ff-change-phuchoang2603

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating OpenSpec change artifacts one by one is slow and error-prone, especially when artifacts depend on each other. This Skill fast-forwards the process by generating every artifact required before implementation in a single workflow. ## 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 artifact in dependency order. - Instruction-Driven Generation: Reads per-artifact templates, rules, and context from openspec instructions and writes files to the resolved output paths, delegating to other skills when instructed. - Store-Aware Operation: Supports registered OpenSpec stores via --store <id> flags discovered with openspec store list --json. - Use Case: A developer says "add user authentication" and the Skill creates the change scaffold, 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 artifacts needed for implementation 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: it calls openspec new change, reads the dependency graph from openspec status --json, and creates each required artifact in order using openspec instructions. It finishes by showing the final change status.

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 required set. Artifacts marked skipped or conditionally optional are left out.

Does openspec fast-forward work with registered stores?▼

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

What happens if 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 skill treats it as satisfied and never attempts to create it.

Why does an OpenSpec artifact show done but its dependencies are missing?▼

The status command checks file existence only, so writing tasks.md early marks tasks done even if specs was never written. The skill relies on each artifact's requires edges, not its status, to determine the true required set.