openspec-ff-change

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

Updated Apr 20, 2020
One-click install
npx skills add https://github.com/UnterrainerInformatik/java-rdb-utils --skill openspec-ff-change-unterrainerinformatik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/UnterrainerInformatik/java-rdb-utils/tree/main/.claude/skills/openspec-ff-change
Command: npx skills add https://github.com/UnterrainerInformatik/java-rdb-utils --skill openspec-ff-change-unterrainerinformatik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating an OpenSpec change normally requires stepping through each artifact (proposal, specs, tasks) one at a time. This Skill fast-forwards the process by generating every artifact required before implementation in a single workflow. ## 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: Fetches per-artifact instructions, templates, and rules from openspec instructions so each file follows the correct schema. - Interactive Clarification: Derives a kebab-case change name from a plain-language description and asks the user when intent is unclear. - Use Case: You describe "add user authentication" and the Skill scaffolds the change, writes the proposal, design, and tasks artifacts, then reports the change is ready for implementation. ## Quick Start Ask the assistant to fast-forward an OpenSpec change by describing what you want to build, for example: create an OpenSpec change 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?▼

Use the fast-forward workflow: run `openspec new change <name>`, then check `openspec status --change <name> --json` for the artifact build order, and create each ready artifact using `openspec instructions` until all applyRequires artifacts are done.

What is the openspec CLI used for in spec-driven development?▼

The openspec CLI scaffolds change directories, reports artifact status and dependencies as JSON, and provides per-artifact instructions, templates, and rules. It drives a structured workflow from proposal through tasks before implementation begins.

Does this workflow require the openspec CLI installed?▼

Yes, the Skill requires the openspec CLI to be available. Every step, from creating the change directory to fetching artifact instructions and checking status, is executed through openspec commands.

What happens if a change with the same name already exists?▼

The workflow suggests continuing the existing change instead of creating a duplicate. You can then resume artifact creation from the current status reported by `openspec status --change <name> --json`.

Why should context and rules not be copied into artifact files?▼

The context and rules fields from `openspec instructions` are constraints guiding how you write, not content for the file. Copying them into artifacts would pollute the output; only the template structure should be filled in.