openspec-ff-change

Create OpenSpec implementation artifacts in dependency-aware order.

6|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/remiverdiesen/ark-fork --skill openspec-ff-change-remiverdiesen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/remiverdiesen/ark-fork/tree/main/.claude/skills/openspec-ff-change
Command: npx skills add https://github.com/remiverdiesen/ark-fork --skill openspec-ff-change-remiverdiesen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the repetitive back-and-forth of creating OpenSpec implementation artifacts one at a time. It helps you move from a vague change request to a complete, apply-ready artifact set with minimal manual coordination.

Core Features & Use Cases

  • Fast-Forward Artifact Creation: Creates the full set of required OpenSpec artifacts instead of stopping after a single file.
  • Dependency-Aware Sequencing: Reads status and instruction data so artifacts are produced in the correct order.
  • Workflow Support: Useful when starting a new change, continuing an existing change, or preparing implementation work for a larger feature.

Quick Start

Tell me what change you want to build or fix, and I will create the OpenSpec change and generate every required artifact in the correct order.

Frequently Asked Questions about openspec-ff-change

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

FAQPage Schema
How do I generate all OpenSpec artifacts for a change request at once?

To generate OpenSpec artifacts in one pass, you provide a change request and the system creates the complete, apply-ready artifact set. This removes the repetitive back-and-forth of creating individual files manually.

Do I need the openspec CLI to scaffold implementation artifacts?

Yes, generating apply-ready OpenSpec implementation artifacts requires the openspec CLI. The process also relies on task tracking and repeated status checks to ensure correct dependency-aware sequencing.

How does dependency-aware sequencing work for change management scaffolding?

Dependency-aware sequencing reads status and instruction data to produce implementation artifacts in the correct order. This ensures that your change management scaffolding is generated accurately without missing prerequisite files.

What is the best way to plan implementation workflows for a new feature change?

The best way to plan implementation workflows is to request the full artifact set for your change. The system handles change planning and scaffold generation, moving you from a vague request to apply-ready outputs.

Can I continue an existing OpenSpec change and generate the remaining artifacts?

Yes, you can continue an existing OpenSpec change by requesting the remaining artifacts. The system reads current status data and generates the missing implementation files in the correct dependency-aware sequence.