openspec-ff-change

Generate OpenSpec artifacts in dependency order for a change.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/oalansilva/crypto --skill openspec-ff-change-oalansilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/oalansilva/crypto/tree/main/.codex/skills/openspec-ff-change
Command: npx skills add https://github.com/oalansilva/crypto --skill openspec-ff-change-oalansilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This command-line workflow lets you fast-track OpenSpec artifact creation so you can implement changes faster without manual scaffolding.

Core Features & Use Cases

  • Automated artifact scaffolding: Generate all required OpenSpec artifacts in one go.
  • Dependency-aware: Builds artifacts in the correct order, respecting dependencies.
  • Use Case: When planning a change, run this to bootstrap the full artifact set for implementation.

Quick Start

Use the openspec-ff-change command to initialize a new change and automatically scaffold all artifacts.

Frequently Asked Questions about openspec-ff-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I auto-generate OpenSpec artifacts for a new change?

The openspec-ff-change command fast-forwards OpenSpec artifact creation by automatically scaffolding all required files into the openspec/changes/<name>/ directory using predefined templates in dependency order.

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

Using an automated CLI workflow ensures OpenSpec artifacts are generated in the correct dependency sequence, preventing missing prerequisite files and streamlining the planning phase for a new change.

Do I need to manually define dependencies when scaffolding OpenSpec artifacts?

No, the CLI handles dependency management internally by prompting for missing input and building the required artifacts in the correct sequence without manual dependency configuration.

Does the openspec-ff-change workflow require external dependencies?

No external dependencies are required to use this workflow, as it operates by enforcing the openspec CLI workflow natively to generate artifacts and manage template-based scaffolding automatically.

How does the CLI handle missing input during artifact generation?

The CLI handles missing input by prompting the user directly during the artifact generation process, ensuring all required data is collected before scaffolding the files into the target directory.

When should I use automated artifact scaffolding for OpenSpec changes?

Automated artifact scaffolding is ideal when planning a new change and you need to bootstrap the full artifact set quickly for implementation without performing manual file creation.