openspec-ff-change

Generate OpenSpec change scaffolds and apply-ready artifacts in dependency order.

1|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/cynkra/cynkra.ai.day --skill openspec-ff-change-cynkra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/cynkra/cynkra.ai.day/tree/main/indietypst/.claude/skills/openspec-ff-change
Command: npx skills add https://github.com/cynkra/cynkra.ai.day --skill openspec-ff-change-cynkra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the friction of manually stepping through OpenSpec artifact creation by generating everything needed to start implementation in one go.

Core Features & Use Cases

  • Change + artifact scaffolding: Creates an OpenSpec change directory from a user-provided change name (kebab-case) or description and prepares all required artifacts.
  • Dependency-aware generation: Retrieves the build order from OpenSpec status and generates artifacts in the correct sequence based on dependencies until all apply.requires artifacts are complete.
  • Hands-off momentum: Minimizes back-and-forth by creating artifacts using schema-provided templates and instructions, only asking the user when critical context is unclear.

Example use case: You want to implement an AI workflow feature (e.g., add a new endpoint or integrate a tool) and need the full set of OpenSpec implementation-ready artifacts immediately.

Quick Start

Tell the assistant what change you want to work on (name in kebab-case or a description), and it will generate the full OpenSpec artifact set in dependency order so you can begin with /opsx:apply.

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 feature at once?

To generate all OpenSpec artifacts at once, provide a change name or description to the skill. It creates the change scaffold and produces apply-ready outputs in dependency order using the OpenSpec CLI.

What is the best way to automate OpenSpec change management workflows?

Automating OpenSpec change management involves using this skill to compute the artifact build order via JSON status and generate each artifact from instruction templates, minimizing manual back-and-forth.

Do I need the openspec CLI to generate apply-ready artifacts in dependency order?

Yes, the openspec CLI is required. The skill runs the CLI to establish the new change directory, compute the dependency build order, and read dependency outputs to generate artifacts.

Can I use plain language to scaffold an OpenSpec implementation workflow?

Yes, you can describe your requested change in plain language or a kebab-case name. The skill uses that input to scaffold the change directory and generate implementation-ready artifacts.

Why does OpenSpec artifact generation require a specific dependency order?

Dependency order is required because artifacts have specific build dependencies. The skill retrieves the build order from OpenSpec status and generates artifacts sequentially until all apply.requires artifacts are complete.

What happens if critical context is unclear during artifact scaffolding?

When critical context is unclear during artifact scaffolding, the skill pauses generation to ask the user for clarification. This prevents errors while maintaining a hands-off approach for clear contexts.