openspec-ff-change

Generates all OpenSpec change artifacts in one pass until implementation-ready.

Updated Jan 5, 2025
One-click install
npx skills add https://github.com/ValorVie/settingZsh --skill openspec-ff-change-valorvie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/ValorVie/settingZsh/tree/main/.gemini/skills/openspec-ff-change
Command: npx skills add https://github.com/ValorVie/settingZsh --skill openspec-ff-change-valorvie

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 dependency graph via openspec status --json, and creates each artifact in dependency order. - Schema-Driven Output: Pulls per-artifact instructions, templates, and rules from openspec instructions so every file follows the correct schema. - Progress Tracking & Clarification: Tracks artifact progress, asks the user when context is unclear, and stops once all applyRequires artifacts are done. - Use Case: You describe "add user authentication" and the Skill scaffolds the change, writes the proposal, design, and tasks files, and reports that 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 requesting it to create all artifacts 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 this fast-forward workflow: it runs openspec new change, reads the artifact dependency order from openspec status --json, then generates each artifact using openspec instructions until every applyRequires artifact is done.

What input does the OpenSpec fast-forward change workflow need?▼

It needs either a kebab-case change name or a plain description of what you want to build. If neither is provided, it asks an open-ended question and derives a kebab-case name from your description.

Does this workflow require the openspec CLI installed?▼

Yes, the openspec CLI is a hard requirement. The workflow shells out to openspec new, openspec status, and openspec instructions, so the CLI must be available in the environment.

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

The workflow suggests continuing the existing change instead of creating a duplicate. It checks for name collisions before scaffolding a new change directory.

When should I not use the fast-forward artifact creation approach?▼

Avoid it when requirements are highly ambiguous and each artifact needs individual review, or when you want to iterate on a proposal before generating downstream specs and tasks.