openspec-ff-change

Generate OpenSpec change artifacts in dependency order until apply-ready.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the repetitive, manual process of creating every OpenSpec artifact required to move a change from scaffold to implementation readiness by automating artifact generation in dependency order.

Core Features & Use Cases

  • End-to-end artifact generation: Creates a new change scaffold, queries artifact status, retrieves artifact instructions, and writes files from templates until apply-ready.
  • Dependency-aware sequencing: Reads dependencies and completed artifacts to determine the correct creation order and re-checks status after each artifact.
  • Interactive clarification and progress tracking: Asks the user for missing intent, uses a Todo tracker for progress, and summarizes completed artifacts and next steps.
  • Use Case: Quickly provision all artifacts for a new feature or bugfix so engineers can begin implementation without stepping through each artifact manually.

Quick Start

Use the skill to create a new change named add-user-auth and generate all required artifacts until the change is apply-ready.

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 artifact creation for implementation setup?

Automating OpenSpec change artifact creation involves running openspec new, querying status, retrieving instructions, and writing template files in dependency order until all apply-ready artifacts report done.

What is the process to fast-forward OpenSpec changes from scaffold to apply-ready?

Fast-forwarding OpenSpec changes requires generating dependent artifacts sequentially: creating a scaffold, checking status JSON, reading dependencies, writing artifact files from templates, and re-checking status until apply-ready.

Does OpenSpec CLI support dependency-aware sequencing when generating change artifacts?

OpenSpec CLI supports dependency-aware sequencing by reading dependencies and completed artifacts to determine the correct creation order, then re-checking artifact status after each file is written.

How do I step through OpenSpec artifact instructions without manual file creation?

Stepping through OpenSpec artifacts without manual file creation uses automation to retrieve instructions JSON, read dependency files, write template-based artifact files, and track progress via a Todo tracker until all artifacts are done.

What are the limitations of automating OpenSpec artifact generation for new changes?

Automating OpenSpec artifact generation requires interactive clarification for missing intent and depends on continuous status re-checking, meaning incomplete dependencies will block the workflow until resolved.

Can I provision all OpenSpec artifacts for a feature bugfix at once?

Provisioning all OpenSpec artifacts for a feature bugfix at once is possible by automating the end-to-end generation process, which queries artifact status, retrieves instructions, and writes files until the change is apply-ready.