openspec-ff-change

Generate OpenSpec implementation artifacts in dependency order from a change.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the rapid creation of implementation artifacts from a user-specified change, eliminating manual, step-by-step scaffolding and ensuring consistency across artifacts.

Core Features & Use Cases

  • Deterministic change scaffolding: Create OpenSpec changes with automated artifact generation to kick off implementation.
  • Dependency-aware sequencing: Artifacts are generated in the correct order as dependencies are satisfied.
  • Guided artifact creation: Reads OpenSpec instructions to fill templates, ensuring consistent structure and metadata.
  • Use Case: When starting a new feature, open a change, run this skill, and obtain a complete set of artifacts ready for implementation and review.

Quick Start

Use the openspec-ff-change skill to scaffold a new change and generate all required artifacts in one run.

  1. If the user's request isn't clear, ask a clarifying question: What change do you want to work on? Describe what you want to build or fix.
  2. Create the change directory: openspec new change "<name>"
  3. Get the artifact build order: openspec status --change "<name>" --json
  4. Create artifacts in sequence until apply-ready:
    • Read artifact instructions with openspec instructions <artifact-id> --change "<name>" --json
    • Create each artifact in dependency order, updating as dependencies complete
  5. Show final status: openspec status --change "<name>"

Frequently Asked Questions about openspec-ff-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate scaffolding for OpenSpec change artifacts?

To automate OpenSpec change scaffolding, this skill uses the OpenSpec CLI to create a change directory, determine dependency-aware build order, and generate structured implementation artifacts sequentially. It reads instructions to fill templates, ensuring consistent metadata and structure across all generated files.

What is dependency-aware sequencing for change management artifacts?

Dependency-aware sequencing in change management ensures implementation artifacts are generated in the correct order as dependencies are satisfied. The skill queries the OpenSpec CLI for build status and creates each artifact only when its prerequisites complete, preventing sequencing errors.

How do I generate implementation-ready artifacts from a change request?

Generating implementation-ready artifacts involves running the OpenSpec CLI to create a change, retrieving the artifact build sequence, and reading instructions for each artifact. The skill scaffolds each file in dependency order until the entire set is apply-ready for review.

Do I need the OpenSpec CLI to scaffold deterministic change workflows?

Yes, you need the OpenSpec CLI to scaffold deterministic change workflows. The skill directly leverages CLI commands to derive change names, query build status, read artifact instructions, and manage dependencies to automate the scaffolding process.

Can I use this automation to skip manual step-by-step artifact creation?

Yes, you can use this automation to skip manual step-by-step artifact creation. It eliminates manual scaffolding by reading OpenSpec instructions to automatically fill templates and generate a complete, consistent set of structured artifacts in a single run.

What are the limitations of automated change scaffolding for software workflows?

Automated change scaffolding requires a clearly defined user-specified change to start; if the request is unclear, it prompts for clarification. It relies entirely on the OpenSpec CLI for status tracking and template instructions, meaning artifacts must conform to predefined OpenSpec structures.