openspec-ff-change

Automate OpenSpec change artifact creation using openspec CLI status and instructions outputs.

Updated Apr 13, 2026

Search Tags:#automation #scaffolding #cli #openspec #change-management #artifact-generation

Ready to run

npx skills add https://github.com/soyrochus/vulgata --skill openspec-ff-change-soyrochus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/soyrochus/vulgata/tree/main/.claude/skills/openspec-ff-change
Command: npx skills add https://github.com/soyrochus/vulgata --skill openspec-ff-change-soyrochus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual, repetitive steps required to create all OpenSpec change artifacts needed to reach an implementation-ready state by automating artifact scaffolding, dependency sequencing, and minimal user clarifications.

Core Features & Use Cases

End-to-end artifact generation: Scaffolds a change directory and creates artifacts in dependency order until all apply-required artifacts are complete.
CLI-driven orchestration: Uses openspec status and openspec instructions JSON to determine build order, read dependencies, and populate templates.
Interactive clarification and tracking: Prompts the user for missing context when necessary and tracks progress with a TodoWrite tool; ideal for quickly bootstrapping implementation work from a brief change description.

Quick Start

Use the skill to create a new change named add-user-auth and generate all required artifacts to reach apply-ready status.

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 OpenSpec change artifact creation?▼

Automate OpenSpec change artifact creation by using a skill that scaffolds the change directory and generates files in dependency order until apply-ready. It leverages openspec status and instructions JSON outputs to sequence creation and validate dependencies automatically.

What is the best way to scaffold an OpenSpec change directory?▼

Scaffolding an OpenSpec change directory is best handled by automating artifact generation in dependency order. This approach uses openspec CLI JSON outputs to determine the build sequence, populate templates, and track progress until all apply-required artifacts are complete.

Do I need the openspec CLI to generate change artifacts?▼

You need the openspec CLI to generate change artifacts because the automation relies on its status and instructions JSON outputs. These CLI commands provide the dependency sequencing and validation data required to scaffold the change directory correctly.

How does OpenSpec dependency sequencing work during scaffolding?▼

OpenSpec dependency sequencing works by reading instructions JSON outputs to determine the exact build order for artifacts. The automation populates templates and validates dependencies sequentially until the change directory reaches an apply-ready state.

Can I bootstrap OpenSpec implementation work from a brief description?▼

You can bootstrap OpenSpec implementation work from a brief description by automating artifact scaffolding. The skill prompts you for missing context when necessary, tracks progress, and generates all required files in dependency order until apply-ready.

Why are my OpenSpec change artifacts not reaching apply-ready status?▼

OpenSpec change artifacts fail to reach apply-ready status when dependencies are not created in the correct sequence. Automating the scaffolding process with CLI JSON validation ensures all required artifacts are generated and validated in proper dependency order.