openspec-ff-change

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

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/caelaxie/agenthub --skill openspec-ff-change-caelaxie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/caelaxie/agenthub/tree/main/.opencode/skills/openspec-ff-change
Command: npx skills add https://github.com/caelaxie/agenthub --skill openspec-ff-change-caelaxie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rapidly creating all implementation-ready OpenSpec artifacts can be slow and error-prone when done step-by-step; this Skill automates the end-to-end artifact creation process from a single change name or user description so you can start implementation faster and with consistent, schema-compliant files.

Core Features & Use Cases

  • One-shot scaffolding: Create a change directory and generate every artifact required for implementation in dependency order using the openspec CLI and provided templates.
  • Dependency-aware generation: Query openspec status and instructions, read completed dependencies for context, and create artifacts until apply.requires are complete.
  • Interactive clarification & tracking: Use an AskUserQuestion flow to clarify unclear inputs and a TodoWrite-style progress tracker to show created artifacts and progress.
  • Use Case: Quickly bootstrap a new feature change (e.g., add-user-auth) by supplying a name or description and receiving a complete set of apply-ready artifacts.

Quick Start

Provide a change name or a plain description and run the skill to generate all required OpenSpec 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 generate all OpenSpec change artifacts from a single prompt?

To generate OpenSpec change artifacts from a single prompt, provide a change name or description to automatically scaffold the change directory and create every required file in dependency order. This one-shot process uses the openspec CLI and provided templates to produce apply-ready artifacts.

What is OpenSpec scaffolding and when do I need it for a new feature change?

OpenSpec scaffolding is the automated process of creating implementation-ready artifacts for a new feature change. You need it when bootstrapping a new change, such as adding user authentication, to ensure consistent, schema-compliant files are generated rapidly and correctly.

Do I need the openspec CLI installed to use automated artifact generation?

Yes, automated artifact generation requires the openspec CLI to query status, read completed dependencies for context, and create files using templates. The CLI drives the dependency-aware generation process until all apply.requires artifacts are complete.

What's the best way to ensure OpenSpec change artifacts are generated in correct dependency order?

The best way to ensure correct dependency ordering is to use an automated scaffolding skill that queries openspec status and instructions, reads completed dependencies for context, and creates artifacts sequentially until apply.requires are complete, preventing manual ordering errors.

What happens if my change description is unclear during OpenSpec artifact generation?

If your change description is unclear during artifact generation, an interactive AskUserQuestion flow prompts you for clarification to ensure accurate scaffolding. A TodoWrite-style progress tracker then displays created artifacts and overall progress.