openspec-ff-change

Generate OpenSpec change artifacts in dependency order via the OpenSpec CLI.

84|18|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/intent-driven-dev/openspec-schemas --skill openspec-ff-change-intent-driven-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/intent-driven-dev/openspec-schemas/tree/main/.opencode/skills/openspec-ff-change
Command: npx skills add https://github.com/intent-driven-dev/openspec-schemas --skill openspec-ff-change-intent-driven-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill speeds up the OpenSpec change workflow by generating all required artifacts for an implementation in one pass, removing the need to manually create each artifact step-by-step.

Core Features & Use Cases

  • End-to-end change scaffolding: creates all necessary artifacts for a new change in one go.
  • Guided, safe automation: asks clarifying questions when input is ambiguous and enforces OpenSpec templates and constraints.
  • Dependency-aware generation: builds artifacts in dependency order and verifies readiness before proceeding.

Quick Start

Provide the change name in kebab-case or a description of what you want to build, and OpenSpec will scaffold and generate all required artifacts.

Frequently Asked Questions about openspec-ff-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate OpenSpec change creation for multiple artifacts at once?

Automating OpenSpec change creation is done by fast-forwarding artifact generation in dependency order, scaffolding all required files in one pass while enforcing template structure and excluding context or rules from final outputs.

What is dependency-aware artifact scaffolding in OpenSpec change management?

Dependency-aware artifact scaffolding generates OpenSpec change files sequentially based on their interdependencies, verifying readiness before proceeding to ensure multiple interdependent artifacts are created and validated correctly.

How do I generate OpenSpec artifacts in dependency order using the CLI?

Generating OpenSpec artifacts in dependency order requires providing a kebab-case change name or description, allowing the CLI to automate end-to-end scaffolding while enforcing template constraints across all generated files.

Does OpenSpec fast-forward generation exclude context and rules from artifact files?

OpenSpec fast-forward generation strictly excludes context and rules from final artifact files, enforcing template structure to ensure only validated, dependency-ordered artifacts are produced during the change creation workflow.

Can I use OpenSpec scaffolding for changes with multiple interdependent artifacts requiring iteration?

OpenSpec scaffolding is designed for new changes with multiple interdependent artifacts requiring validation and iteration, asking clarifying questions when input is ambiguous to safely automate the end-to-end generation process.

What's the best way to scaffold a new OpenSpec change without manual step-by-step artifact creation?

Scaffolding a new OpenSpec change without manual steps involves providing a change name or description, triggering automated end-to-end generation that builds all required artifacts in dependency order with template enforcement.