openspec-ff-change

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

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/zh-impact/agent-feeder --skill openspec-ff-change-zh-impact
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/zh-impact/agent-feeder/tree/main/.claude/skills/openspec-ff-change
Command: npx skills add https://github.com/zh-impact/agent-feeder --skill openspec-ff-change-zh-impact

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 workflow. ## Core Features & Use Cases - Batch Artifact Creation: Runs openspec new change, reads the build order via openspec status --json, and creates each ready artifact in dependency order. - Schema-Driven Output: Pulls per-artifact instructions, templates, and rules from openspec instructions so each file follows the correct schema. - Dependency-Aware Sequencing: Reads completed dependency artifacts for context and stops only when all applyRequires artifacts report done. - Use Case: A developer describes "add user authentication" and receives a fully scaffolded change at openspec/changes/add-user-auth/ with all artifacts ready for implementation. ## Quick Start Ask the assistant to fast-forward an OpenSpec change by describing what you want to build, for example: create all artifacts for a change named add-user-auth.

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?▼

Provide a change name or a description of what you want to build. The skill runs openspec new change, reads the artifact build order from openspec status, and creates each ready artifact in dependency order until all applyRequires artifacts are done.

What input does the OpenSpec fast-forward 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 answer before proceeding.

Does this skill require the openspec CLI installed?▼

Yes, the openspec CLI is a stated compatibility requirement. The workflow shells out to openspec new, openspec status, and openspec instructions commands to scaffold and populate the change directory.

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

The skill's guardrails direct it to suggest continuing the existing change instead of creating a duplicate. It also verifies each artifact file exists after writing before moving to the next one.

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

Avoid it when you need to review and refine each artifact individually, since fast-forwarding makes reasonable decisions autonomously to keep momentum. Use the step-by-step artifact workflow when close human review of each spec is required.