openspec-ff-change

Generate OpenSpec change directories and schema-compliant artifacts in dependency order.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/tungnguyen10/iuh_department --skill openspec-ff-change-tungnguyen10
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/tungnguyen10/iuh_department/tree/main/.agents/skills/openspec-ff-change
Command: npx skills add https://github.com/tungnguyen10/iuh_department --skill openspec-ff-change-tungnguyen10

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the slow, repetitive process of manually creating individual OpenSpec artifacts, cutting down preparation time for implementation significantly.

Core Features & Use Cases

  • Automated Change Scaffolding: Instantly creates a new OpenSpec change directory with the correct kebab-case name from your request.
  • Dependency-Aware Artifact Generation: Produces all required implementation artifacts in the correct order, reading prior completed artifacts for context.
  • Use Case: If you are planning a new user authentication feature for your application, use this Skill to generate all required OpenSpec specs, tasks, and design documents in one go, instead of creating each file manually.

Quick Start

Use the openspec-ff-change skill to generate all required OpenSpec artifacts for your new 'add-user-auth' implementation change.

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 artifact generation for implementation planning?

You can automate OpenSpec artifact generation by using a scaffolding tool that creates the change directory, resolves document dependencies, and outputs schema-compliant planning files in the correct order automatically.

What is the best way to scaffold OpenSpec change directories?

The best way to scaffold OpenSpec change directories is to use an automated generator that applies kebab-case naming and produces all required specs, tasks, and design documents at once instead of manual file creation.

How does dependency resolution work when generating OpenSpec planning documents?

Dependency resolution works by reading prior completed artifacts for context and generating subsequent implementation documents in the correct sequential order required by the OpenSpec schema.

Can I generate all OpenSpec specs and design documents in one go?

Yes, you can generate all OpenSpec specs and design documents in one go by triggering an automated scaffolding process that creates every required implementation artifact simultaneously.

When do I need automated scaffolding for software development change management?

You need automated scaffolding for software development change management when manual creation of individual implementation artifacts becomes too slow or repetitive for your planning workflow.

Do I need to manually create OpenSpec implementation artifacts one by one?

No, you do not need to manually create OpenSpec implementation artifacts one by one because automated scaffolding tools can generate all required schema-compliant files instantly.