skills.rest
igamenovoer
igamenovoerCOMMUNITY
Explore all skills by this author →
GitHub

openspec-ff-change

Generate OpenSpec artifacts in dependency order until apply-ready.

18|3|Updated Mar 5, 2026
Search Tags:#scaffolding#openspec#dependency resolution#artifact generation#cli automation#implementation readiness
One-click install
npx skills add https://github.com/igamenovoer/houmao --skill openspec-ff-change-igamenovoer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/igamenovoer/houmao/tree/main/tests/fixtures/plain-agent-def/skills/openspec-ff-change
Command: npx skills add https://github.com/igamenovoer/houmao --skill openspec-ff-change-igamenovoer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the step-by-step friction of creating all required OpenSpec artifacts for an implementation-ready change by generating everything in one run.

Core Features & Use Cases

  • Scaffold a new OpenSpec change from a user-provided change name (kebab-case) or from a description of what to build.
  • Determine artifact build order automatically by reading OpenSpec status output and respecting dependency sequencing.
  • Create artifacts until the change is apply-ready, including clarification when user input is unclear, then provide a final status summary for next steps.

Use Case: When you want to start implementing immediately, provide what you want to change, and let the Skill generate every artifact needed for implementation without manually creating each one.

Quick Start

Tell the assistant what change you want to work on (use a kebab-case name or describe what you want to build), and it will generate all apply-ready OpenSpec artifacts 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 generate all OpenSpec artifacts for a change without creating each one manually?▼

To generate OpenSpec artifacts automatically, provide a kebab-case change name or description, and the system scaffolds all required artifacts in dependency order until the change is apply-ready.

What is OpenSpec artifact scaffolding and when do I need it for implementation?▼

OpenSpec artifact scaffolding is the automated generation of implementation-ready artifacts in dependency order. You need it when starting a new change and want to skip manual, step-by-step artifact creation.

Do I need the openspec CLI to scaffold artifacts for a new change?▼

Yes, the openspec CLI is required to create the change, read JSON status for applyRequires, determine artifact dependency sequencing, and generate artifacts from instruction templates.

What's the best way to determine dependency order when creating OpenSpec artifacts?▼

The best way to determine dependency order is reading the OpenSpec JSON status output, which allows the scaffolding process to respect dependency sequencing and generate artifacts until all applyRequires are done.

Why does my OpenSpec change scaffold stop before implementation begins?▼

The scaffolding process stops when all applyRequires artifacts reach done status, meaning the change is implementation-ready. It will also pause to request clarification if your initial input is unclear.

Related Skills

Explore More Software Engineering Skills→
wishx127wishx127

openspec-new-change

Scaffold a new OpenSpec change with artifact sequencing and status guidance.

Community
Intermediate
LippyyDevLippyyDev
1

openspec-ff-change

Scaffold OpenSpec change artifacts in dependency order using status queries.

Community
Advanced
evandrodevbrevandrodevbr
1

openspec-continue-change

Create the next OpenSpec workflow artifact from an existing change state.

Community
Advanced
nfenfe
139

openspec-ff-change

Generate OpenSpec implementation artifacts in dependency order from CLI status JSON.

Official
Intermediate