openspec-ff-change

Generate OpenSpec change artifacts from a change name or description.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/futuretea/x-project --skill openspec-ff-change-futuretea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/futuretea/x-project/tree/main/.claude/skills/openspec-ff-change
Command: npx skills add https://github.com/futuretea/x-project --skill openspec-ff-change-futuretea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many OpenSpec workflows require creating multiple interdependent artifacts manually using the CLI, which is slow and error-prone; this Skill automates the sequence so implementable artifacts are produced quickly and consistently.

Core Features & Use Cases

  • Automated Change Scaffolding: Create a new change directory and generate all required artifacts in dependency order using openspec CLI commands.
  • Dependency-aware Artifact Creation: Query status and instructions, read completed dependencies for context, and populate files from provided templates until apply-ready artifacts are complete.
  • Use Case: Quickly bootstrap an implementation-ready change (e.g., add-user-auth) by providing a name or description to produce tasks, specifications, and other artifacts without stepping through each artifact manually.

Quick Start

Provide a kebab-case change name or a short description and ask the Skill to generate all required OpenSpec artifacts for that change, for example create change add-user-auth.

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 OpenSpec change artifacts automatically from a single command?

OpenSpec artifact generation creates all required files from a single change name by running openspec CLI commands, bootstrapping the change directory and producing implementation-ready artifacts in correct dependency order.

What is the best way to bootstrap an OpenSpec change directory with dependency ordering?

Bootstrapping an OpenSpec change directory involves querying status and instructions, reading completed dependencies for context, and populating templates until apply-ready artifacts are complete and correctly ordered.

Do I need the openspec CLI installed to scaffold change artifacts?

Yes, the openspec CLI is required because this automation invokes openspec new change, openspec status, and openspec instructions commands to sequence and generate the required change artifacts.

How does automated change scaffolding handle interdependent artifact creation?

Automated change scaffolding handles interdependent artifacts by following artifact dependency ordering, querying instructions, reading completed dependencies for context, and prompting for user clarification only when an instruction requires input.

Can I create implementation-ready OpenSpec files from a short description instead of a formatted name?

Yes, you can provide either a kebab-case change name or a short description to generate implementation-ready OpenSpec artifacts, allowing the automation to bootstrap tasks and specifications directly from your input.