openspec-ff-change

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

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/twaananen/6dof-drone-sim --skill openspec-ff-change-twaananen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/twaananen/6dof-drone-sim/tree/main/.agents/skills/openspec-ff-change
Command: npx skills add https://github.com/twaananen/6dof-drone-sim --skill openspec-ff-change-twaananen

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 from 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 via openspec instructions so each file follows the correct structure. - Interactive Clarification: Asks the user what they want to build when no change name or description is provided, deriving a kebab-case change name automatically. - Use Case: A developer says "fast-forward a change for adding user authentication" and receives a complete openspec/changes/add-user-auth/ directory 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 that adds 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?▼

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 --json, and creates each 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-language description of what you want to build. If neither is given, it asks an open-ended question and derives a kebab-case name from your answer.

Does this skill require the openspec CLI installed?▼

Yes, the openspec CLI is required. The skill shells out to commands like openspec new change, openspec status --json, and openspec instructions to scaffold and populate the change directory.

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

The skill suggests continuing the existing change instead of creating a duplicate. It checks the change directory before proceeding with artifact generation.

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

Avoid it when you need to review or discuss each artifact individually, such as for complex or high-risk changes. Fast-forwarding is best when requirements are clear and you want to reach implementation quickly.