openspec-ff-change

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

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/thewoolleyman/personal-knowledge-base --skill openspec-ff-change-thewoolleyman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/thewoolleyman/personal-knowledge-base/tree/main/.claude/skills/openspec-ff-change
Command: npx skills add https://github.com/thewoolleyman/personal-knowledge-base --skill openspec-ff-change-thewoolleyman

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 artifact in dependency order until all applyRequires artifacts are done. - Schema-Driven Output: Fetches per-artifact instructions, templates, and rules via openspec instructions so each file follows the correct structure. - Interactive Clarification: Derives a kebab-case change name from a plain-language description and asks the user when context is unclear. - Use Case: A developer says "add 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, for example: create all OpenSpec 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?▼

Run the fast-forward workflow with a change name or description. It scaffolds the change with `openspec new change`, reads the artifact build order from `openspec status --json`, and creates each artifact in dependency order until all apply-required 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 structures proposals, designs, and task lists so implementation can begin from a complete specification.

Does the fast-forward workflow require the openspec CLI installed?▼

Yes, the workflow depends entirely on the openspec CLI for scaffolding, status checks, and artifact instructions. Without it installed and available on the PATH, none of the artifact creation steps can run.

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 then resumes artifact creation based on the current status of the existing change directory.

When should I step through artifacts individually instead of fast-forwarding?▼

Step through individually when artifacts need careful review or significant user decisions at each stage. Fast-forwarding is better when requirements are clear and you want to reach implementation quickly with reasonable default decisions.