openspec-ff-change

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

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/shrek-abaper/sap-nexus-agent --skill openspec-ff-change-shrek-abaper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/shrek-abaper/sap-nexus-agent/tree/main/.comet/skills/skills/openspec-ff-change
Command: npx skills add https://github.com/shrek-abaper/sap-nexus-agent --skill openspec-ff-change-shrek-abaper

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 guided run. ## Core Features & Use Cases - Batch Artifact Creation: Runs openspec new change, reads the dependency-ordered artifact list via openspec status --json, and creates each artifact using the schema-driven instructions from openspec instructions. - Dependency-Aware Sequencing: Reads completed dependency artifacts for context before writing new ones, and stops only when every artifact in applyRequires is marked done. - Interactive Clarification: Derives a kebab-case change name from a plain-language description and asks the user for clarification when intent is unclear. - Use Case: You describe "add OAuth login support" and the Skill scaffolds the change, writes the proposal, design, and tasks files, 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 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, then loops through openspec status and openspec instructions to create each artifact in dependency order until every artifact in applyRequires is done.

What is the difference between fast-forward and step-by-step OpenSpec artifact creation?▼

Fast-forward generates every artifact needed for implementation in one continuous run, while the step-by-step approach pauses after each artifact for individual review. Both use the same openspec CLI instructions and templates.

Does this workflow require the openspec CLI to be installed?▼

Yes, the openspec CLI is a hard requirement. The workflow shells out to openspec new, openspec status, and openspec instructions commands, so it cannot function without the CLI installed and available.

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

The workflow detects the existing change and suggests continuing that change instead of creating a duplicate. It will not silently overwrite an existing change directory.

Why should context and rules blocks not appear in generated artifacts?▼

The context and rules fields from openspec instructions are constraints guiding the author, not file content. Copying them into artifacts would pollute the spec with internal scaffolding meant only to shape the writing.