openspec-ff-change

Scaffold OpenSpec artifacts from a change name in dependency order.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/martinsson/checkin-automation --skill openspec-ff-change-martinsson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/martinsson/checkin-automation/tree/main/.claude/skills/openspec-ff-change
Command: npx skills add https://github.com/martinsson/checkin-automation --skill openspec-ff-change-martinsson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This fast-forward workflow creates all OpenSpec artifacts needed for a change, eliminating the manual scaffolding and multiple setup steps.

Core Features & Use Cases

  • Automates scaffold generation for openspec changes from a single change name.
  • Builds artifact files in correct dependency order and tracks progress until completion.
  • Supports handling unclear input by prompting the user and deriving a kebab-case change name.

Quick Start

Provide a change name in kebab-case and I will scaffold all artifacts with openspec, then iteratively build dependencies in order.

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 all OpenSpec artifacts for a new change from a single name?

OpenSpec artifact scaffolding is automated by providing a kebab-case change name, which generates the full artifact suite, handles dependency order, and produces ready-to-edit files without manual setup.

What is the fastest way to generate code-generation artifacts for change management?

Automated code-generation artifact creation accelerates change management by reading dependency graphs, applying template constraints, and iteratively building required artifacts until the entire suite is complete.

Can I use this automated scaffolding if my change name input is unclear?

Yes, the scaffolding workflow supports unclear input by prompting you interactively to derive a correctly formatted kebab-case change name before generating the artifacts.

How does dependency resolution work when generating OpenSpec artifacts?

Dependency resolution works by reading the dependency graph and building artifact files in the correct sequential order, tracking progress iteratively until all required dependencies and artifacts are satisfied.

Do I need to manually track progress when creating multiple OpenSpec artifacts?

No, the automated scaffolding process records progress internally, iteratively building artifacts in dependency order until all required files are completely generated and ready for editing.