openspec-ff-change

Name: openspec-ff-change
Availability: InStock
Author: kevinxo328

Generate OpenSpec change artifacts in dependency order using openspec CLI outputs.

5|Updated Sep 17, 2022

Search Tags:#automation #scaffolding #cli #devtools #openspec #artifact-generator

Ready to run

npx skills add https://github.com/kevinxo328/mercari-scraper --skill openspec-ff-change-kevinxo328

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/kevinxo328/mercari-scraper/tree/main/.gemini/skills/openspec-ff-change
Command: npx skills add https://github.com/kevinxo328/mercari-scraper --skill openspec-ff-change-kevinxo328

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes repetitive manual work when preparing an OpenSpec change by automatically generating every artifact required for implementation so engineers can start coding sooner and avoid manual scaffolding errors.

Core Features & Use Cases

End-to-end artifact generation: Scaffolds a change directory and creates artifacts in dependency order until apply-ready using openspec CLI outputs.
Dependency-aware workflow: Queries openspec status and instructions JSON to resolve artifact dependencies and templates, re-checking status after each artifact.
Interactive clarification: Prompts the user when input is unclear and records progress with a TodoWrite-style tracker.
Use Case: When you want to add a new feature or fix and need all change artifacts (tasks, specs, docs) created automatically to begin implementation.

Quick Start

Generate a new OpenSpec change named add-user-auth and create all required artifacts until 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 automatically generate all OpenSpec change artifacts for implementation readiness?▼

OpenSpec change artifacts are the tasks, specs, and docs files required before implementation begins. Generating them in dependency order ensures all templates and apply-require checks are satisfied sequentially without manual scaffolding errors.

How do I scaffold an OpenSpec change directory and create artifacts in dependency order?▼

To scaffold an OpenSpec change directory, the automation queries openspec status and instructions JSON outputs to determine artifact templates and order, re-checking status after each artifact is created until the entire set is apply-ready.

Do I need the openspec CLI available to automate change artifact generation?▼

Yes, the openspec CLI is required to automate change artifact generation. The workflow relies on openspec status and openspec instructions JSON outputs to determine artifact order, templates, and apply-require checks throughout the scaffolding process.

What's the best way to avoid manual scaffolding errors when preparing an OpenSpec change?▼

The best way to avoid manual scaffolding errors is using end-to-end artifact generation that applies dependency-aware workflow logic. It queries openspec CLI outputs to resolve dependencies and templates, re-checking status after each artifact creation step.

Can I get interactive clarification when generating OpenSpec change artifacts?▼

Yes, interactive clarification is supported during OpenSpec change artifact generation. The workflow prompts the user when input is unclear and records progress using a TodoWrite-style tracker to ensure all required artifacts are created correctly.