openspec-ff-change

Create all required OpenSpec implementation artifacts from a change name or description.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/kamansoft/vite-plugin-flatwave-react --skill openspec-ff-change-kamansoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/kamansoft/vite-plugin-flatwave-react/tree/main/.cursor/skills/openspec-ff-change
Command: npx skills add https://github.com/kamansoft/vite-plugin-flatwave-react --skill openspec-ff-change-kamansoft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the creation of all necessary artifacts for implementation in OpenSpec, saving time and reducing manual steps.

Core Features & Use Cases

  • Fast-Forward Artifact Creation: Quickly generate all required artifacts for implementation without individual steps.
  • Input Flexibility: Accepts change names or descriptions to derive the artifact name.
  • Automatic Build Order: Determines the correct sequence for artifact creation based on dependencies.
  • Progress Tracking: Monitors and reports progress through the artifact creation process.
  • User Input Handling: Asks for clarification if context is unclear, ensuring accurate artifact creation.

Quick Start

Run the openspec-ff-change skill with the change name or description to create all artifacts needed for implementation.

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 creation for project setup?

Automating OpenSpec artifact creation is done by providing a change name or description, which derives the artifact name and builds all required implementation files in the correct dependency sequence.

What is the best way to generate multiple implementation artifacts in OpenSpec?

Generating multiple implementation artifacts is best handled by fast-forwarding the process, which determines the correct build order and tracks progress automatically without requiring individual manual steps.

Do I need the OpenSpec CLI to create implementation artifacts?

Yes, the OpenSpec CLI is required as a dependency to create implementation artifacts, as the process relies on it to handle artifact dependencies and ensure accurate project onboarding.

How does the artifact creation process handle unclear input or context?

Handling unclear input during artifact creation involves asking the user for clarification, ensuring the derived artifact name and implementation context remain accurate and aligned with project requirements.

Can I track progress while generating OpenSpec implementation files?

Tracking progress while generating OpenSpec implementation files is supported natively, monitoring the automatic build order and reporting status throughout the artifact creation sequence.

Are there limitations when deriving artifact names from change descriptions?

Deriving artifact names from change descriptions requires sufficient context; if the input is ambiguous, the process pauses to request clarification, preventing incorrect artifact creation.