openspec-ff-change

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

5|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Catsofsuffering/CCGS --skill openspec-ff-change-catsofsuffering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/Catsofsuffering/CCGS/tree/main/.agents/skills/openspec-ff-change
Command: npx skills add https://github.com/Catsofsuffering/CCGS --skill openspec-ff-change-catsofsuffering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the tedious, error-prone process of creating every OpenSpec change artifact in the correct dependency order so implementation can begin without manual artifact-by-artifact work.

Core Features & Use Cases

  • Full fast-forward generation: Iteratively creates all artifacts required for implementation until the change is apply-ready by querying openspec status and instructions.
  • Dependency-aware sequencing: Reads completed artifacts for context, honors dependency ordering, and re-checks status after each artifact is created.
  • Interactive clarification and progress tracking: Prompts the user when input is unclear and uses a TodoWrite-style tracker to show progress.
  • Use case: Quickly scaffold a new change (for example, add-user-auth) and produce tasks, spec files, and other implementation artifacts so a team can start execution immediately.

Quick Start

Provide a change name or a short description (for example, create a change named add-user-auth) and run the fast-forward process to generate all artifacts until ready for implementation.

Frequently Asked Questions about openspec-ff-change

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

FAQPage Schema
How do I generate all OpenSpec change artifacts in the correct dependency order?

To generate all OpenSpec change artifacts in dependency order, provide a change name and run the fast-forward process. The skill queries openspec status and instructions to iteratively create spec files and tasks until apply-ready.

What is the best way to automate OpenSpec change artifact creation for a new feature?

Automating OpenSpec change artifact creation is handled by fast-forwarding the generation of all required implementation files. It reads completed artifacts for context, honors dependency ordering, and re-checks status after each artifact is created.

Do I need the openspec CLI to use this fast-forward artifact generation skill?

Yes, you need the openspec CLI installed to use this artifact generation skill. It relies on openspec status and openspec instructions commands to read templates, resolve schemas, and track artifact dependency ordering.

Can I track progress and handle user clarifications during OpenSpec artifact generation?

Yes, you can track progress and handle user clarifications during OpenSpec artifact generation. The skill uses a TodoWrite-style tracker to display progress and prompts you interactively when input is unclear or missing.

Why does my OpenSpec change workflow fail when artifacts are created out of order?

OpenSpec change workflows fail when artifacts are created out of order because dependencies are unmet. This skill solves the problem by querying openspec status, sequencing artifact creation by dependency, and re-checking readiness after each step.

What are the limitations of automating OpenSpec change artifact generation?

A limitation of automating OpenSpec change artifact generation is that it cannot proceed without the openspec CLI. Generation stops when apply-ready artifacts are complete, requiring manual implementation execution to begin afterward.