openspec-ff-change

Generate OpenSpec artifacts for a change in dependency order using templates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a fast path to generate all OpenSpec artifacts for a change, eliminating manual, step-by-step scaffolding.

Core Features & Use Cases

  • One-shot scaffolding: Creates all necessary artifacts in dependency order.
  • Dependency-aware generation: Resolves dependencies and applies per-artifact templates.
  • Guided artifact creation: Fetches per-artifact instructions and formats outputs for implementation.

Quick Start

Use the openspec-ff-change skill to rapidly scaffold a new change. Steps include: run openspec new change "<name>", check status with openspec status --change "<name>" --json, and iteratively create artifacts following openspec instructions.

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 a new change?

Automating OpenSpec artifact generation uses the openspec-ff-change Skill to scaffold all artifacts in one workflow. It reads per-artifact instructions, resolves dependencies, and writes implementation-ready outputs using the OpenSpec CLI.

What is the best way to scaffold all OpenSpec artifacts in dependency order?

The best way to scaffold all OpenSpec artifacts in dependency order is using an automated one-shot workflow. It eliminates manual step-by-step creation by resolving dependencies and applying templates to produce implementation-ready artifacts.

Do I need the OpenSpec CLI to bootstrap changes and manage artifact dependencies?

Yes, you need the OpenSpec CLI to bootstrap changes and manage artifact dependencies. The Skill enforces CLI usage to run commands like openspec new change, check status, and iteratively create artifacts following instructions.

Can I generate implementation-ready artifacts for OpenSpec in a single workflow?

Yes, you can generate implementation-ready artifacts for OpenSpec in a single workflow. The Skill fetches per-artifact instructions, respects dependency order, and formats outputs according to templates while enforcing constraints.

Why does manual step-by-step scaffolding fail when bootstrapping OpenSpec changes?

Manual step-by-step scaffolding fails because it ignores dependency order and template constraints. Automated scaffolding resolves dependencies, reads per-artifact instructions, and writes outputs according to templates to ensure implementation readiness.