openspec-ff-change

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

Updated Nov 7, 2023
One-click install
npx skills add https://github.com/lstellway/nixfiles --skill openspec-ff-change-lstellway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/lstellway/nixfiles/tree/main/modules/home-manager/claude/skills/openspec-ff-change
Command: npx skills add https://github.com/lstellway/nixfiles --skill openspec-ff-change-lstellway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating an OpenSpec change normally requires stepping through each artifact (proposal, design, tasks) one at a time. This Skill fast-forwards the process by generating every artifact required before implementation in a single run, so you can go from idea to implementation-ready change without manual back-and-forth. ## Core Features & Use Cases - Batch Artifact Creation: Runs openspec new change, reads the build order via openspec status --json, and creates each artifact in dependency order until all applyRequires artifacts are done. - Schema-Driven Output: Pulls per-artifact instructions, templates, and rules from openspec instructions so each file follows the correct structure without copying internal context blocks. - Interactive Clarification: Asks the user open-ended questions when the change goal or artifact context is unclear, deriving kebab-case change names from plain descriptions. - Use Case: You describe "add user authentication" and the Skill scaffolds openspec/changes/add-user-auth/, generates the proposal, design, and tasks artifacts, and reports the change is ready for implementation. ## Quick Start Ask the assistant to fast-forward an OpenSpec change, for example: create all artifacts for a change named add-user-auth so it is ready to implement.

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 flow with a change name or a description of what you want to build. It runs openspec new change, reads the artifact build order from openspec status --json, and creates each artifact in dependency order until everything required for implementation is done.

What does the openspec status JSON output tell this workflow?

The openspec status --json output provides the applyRequires array listing artifact IDs needed before implementation, plus the full artifacts list with status and dependencies. The workflow uses this to decide which artifact to create next and when to stop.

Does this Skill require the openspec CLI to be installed?

Yes, the openspec CLI is a hard requirement. Every step, from scaffolding the change directory to fetching per-artifact instructions and templates, is executed through openspec commands such as new, status, and instructions.

What happens if the change name I provide already exists?

If a change with that name already exists, the workflow suggests continuing that existing change instead of creating a duplicate. It does not overwrite or recreate the existing change directory.

When should I not use the fast-forward approach for OpenSpec changes?

Avoid fast-forwarding when you need to review and refine each artifact individually, such as for complex or high-risk changes. The step-by-step artifact flow gives more control over each document's content before proceeding.