openspec-ff-change

Scaffold OpenSpec changes by generating all required artifacts in dependency order.

39|6|Updated Apr 22, 2025
One-click install
npx skills add https://github.com/danielsogl/copilot-workflow-demo --skill openspec-ff-change-danielsogl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/danielsogl/copilot-workflow-demo/tree/main/.github/skills/openspec-ff-change
Command: npx skills add https://github.com/danielsogl/copilot-workflow-demo --skill openspec-ff-change-danielsogl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically scaffolds OpenSpec changes by generating every required artifact in one go, saving time and reducing setup friction.

Core Features & Use Cases

  • Creates the change structure at openspec/changes/<name> and computes the artifact build order using openspec status.
  • Generates artifacts in dependency order, ensuring apply-ready artifacts are created only after dependencies are resolved, while handling prompts for unclear inputs.
  • Supports end-to-end workflows for rapid implementation readiness, with guardrails to prevent partial or inconsistent outputs.

Quick Start

Run the openspec CLI to create a new change and automatically scaffold all required artifacts in one go.

Frequently Asked Questions about openspec-ff-change

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

FAQPage Schema
How do I scaffold OpenSpec change artifacts automatically?

Scaffold OpenSpec change artifacts automatically by providing a change name; the automation computes dependencies and generates all required files in the correct order. It uses the openspec CLI to create the change structure and produce ready-to-use outputs.

What is the best way to manage OpenSpec change creation end-to-end?

Managing OpenSpec change creation end-to-end involves computing artifact build order and resolving dependencies before generating files. This approach enforces change flow constraints, prompts for unclear inputs, and prevents partial or inconsistent outputs.

Does OpenSpec scaffolding handle artifact dependencies in the right order?

OpenSpec scaffolding handles artifact dependencies by computing the build order and producing apply-ready artifacts only after dependencies are resolved. This ensures files are generated sequentially and prevents incomplete change structures.

Can I generate all required OpenSpec files from a single change name?

Generate all required OpenSpec files from a single change name by running the openspec CLI. The automation reads artifact templates, computes dependencies, and scaffolds the entire change structure in one go.

Why does OpenSpec change scaffolding prevent partial outputs?

OpenSpec change scaffolding prevents partial outputs by enforcing change flow constraints and resolving artifact dependencies before generating files. Guardrails ensure inconsistent or incomplete change structures are never produced.

What limitations exist when automating OpenSpec artifact generation?

Automating OpenSpec artifact generation requires clear inputs; the tool prompts when inputs are unclear. It also keeps sensitive context out of final files and relies on the openspec CLI to compute the correct artifact build order.