openspec-ff-change

Generate OpenSpec implementation scaffolding and artifacts from a change name.

6|1|Updated Dec 19, 2025
One-click install
npx skills add https://github.com/ilaziness/vexo --skill openspec-ff-change-ilaziness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/ilaziness/vexo/tree/main/.crush/skills/openspec-ff-change
Command: npx skills add https://github.com/ilaziness/vexo --skill openspec-ff-change-ilaziness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the slow, step-by-step overhead of creating OpenSpec artifacts by fast-forwarding through artifact creation until everything required for implementation is ready.

Core Features & Use Cases

  • Change scaffolding: Creates a new OpenSpec change directory using a user-provided change name.
  • Artifact build ordering: Uses OpenSpec status to determine the correct dependency order and stops only when all required apply-ready artifacts are done.
  • Schema-driven outputs: Generates each artifact file by pulling its instructions and template, then writing the artifact content without copying context/rules into the output.
  • Interactive clarification: Asks for clarification if required user input for an artifact is unclear.
  • Use case: When you want to implement a new feature or fix and need all the OpenSpec scaffolding and artifacts created quickly, without manually creating each one.

Quick Start

Tell me what change you want to work on (a short kebab-case name or a description), and I will fast-forward OpenSpec artifact creation until the change is 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 artifacts for a new change at once?

To generate OpenSpec artifacts in one go, provide a change name or description and the CLI fast-forwards through dependency-ordered artifact creation, pulling instructions and templates until all required apply-ready artifacts are done.

What is the best way to automate change scaffolding with OpenSpec?

Automating change scaffolding with OpenSpec requires running status and instructions queries in JSON form to determine dependency order, then rendering templates to write artifact files without copying context or rules into the output.

Do I need the OpenSpec CLI to create implementation scaffolding in a single session?

Yes, creating implementation scaffolding in a single session requires the OpenSpec CLI to query artifact status, fetch dependency-ordered instructions, and render templates until all apply-required artifacts are marked done.

How does dependency ordering work when creating OpenSpec artifacts?

Dependency ordering uses OpenSpec status queries to sequence artifact creation, ensuring each file is generated by pulling its specific instructions and template only when its dependencies are apply-ready.

What happens if required input for an OpenSpec artifact is unclear?

If required input for an artifact is unclear, the process pauses to ask for interactive clarification before writing the artifact content, ensuring the generated scaffolding matches the intended change description.

Can I use a descriptive sentence instead of a kebab-case name to start OpenSpec artifact generation?

Yes, you can provide either a short kebab-case name or a full description to initiate the change directory creation, which then drives the fast-forwarding generation of all required OpenSpec artifacts.