openspec-ff-change

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of all OpenSpec change artifacts so contributors can move from idea to implementation-ready state without manually stepping through each artifact and dependency.

Core Features & Use Cases

  • End-to-end Artifact Generation: Scaffolds a new change and iteratively creates required artifacts in dependency order until apply-ready.
  • Guided Clarification & Progress Tracking: Uses interactive prompts to clarify unclear requirements and a todo tracker to show progress for each artifact.
  • Use Case: Quickly onboard a feature request or bug fix by generating templates, instructions, and supporting files required by the OpenSpec workflow so implementers can start work immediately.

Quick Start

Use this skill to create an OpenSpec change named add-user-auth and generate all required artifacts for implementation.

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 for a new feature request?

To generate OpenSpec change artifacts, this Skill scaffolds a new change and iteratively creates required files in dependency order until apply-ready. It uses interactive prompts to clarify requirements and a todo tracker to monitor artifact creation progress.

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

Automating OpenSpec change workflows is handled by generating templates, instructions, and supporting files sequentially based on dependency resolution. This allows contributors to move from an idea to an implementation-ready state without manually stepping through each artifact.

Do I need the openspec CLI to create implementation-ready change files?

Yes, creating apply-ready change files requires the openspec CLI. The Skill depends on running and parsing openspec status and openspec instructions JSON outputs to determine dependencies and generate the correct artifacts.

Can I use this to scaffold a bug fix with multiple file dependencies?

Yes, you can scaffold bug fixes or features with file dependencies. The Skill resolves artifact dependencies iteratively, prompting for clarification on unclear requirements to ensure all supporting files are created in the correct order.

How does interactive clarification work when generating change artifacts?

Interactive clarification works by prompting users for input when requirements are unclear during artifact generation. This ensures the generated OpenSpec change files accurately reflect the needed implementation details before reaching the apply-ready state.