openspec-ff-change

Generate OpenSpec change artifacts in dependency order until implementation-ready.

Updated Nov 12, 2025
One-click install
npx skills add https://github.com/artagon/artagon-vscode-profiles --skill openspec-ff-change-artagon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/artagon/artagon-vscode-profiles/tree/main/agents/skills/openspec-ff-change
Command: npx skills add https://github.com/artagon/artagon-vscode-profiles --skill openspec-ff-change-artagon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the step-by-step overhead of creating all required OpenSpec artifacts for a change by generating everything needed in one focused flow.

Core Features & Use Cases

  • Change scaffold creation: Creates an OpenSpec change directory using a derived kebab-case change name.
  • Dependency-aware artifact generation: Queries artifact build order, then generates artifacts in the correct dependency sequence until everything needed for implementation is ready.
  • User clarification when context is unclear: Prompts for missing or ambiguous input to keep artifact creation accurate while maintaining momentum.

Quick Start

Tell the assistant what change you want to build or fix (including a kebab-case name if you have one) and it will create all implementation-ready OpenSpec artifacts automatically.

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 OpenSpec artifacts for a change scaffold automatically?

Generate OpenSpec artifacts automatically by providing a change description; the tool fast-forwards creation of an implementation-ready change workspace in a single focused flow.

What is dependency ordering for artifact generation and why is it needed?

Dependency ordering queries the required build sequence and generates artifacts in the correct order, ensuring context dependencies are resolved before apply-ready requirements are satisfied.

Do I need the openspec CLI installed to create implementation-ready artifacts?

Yes, you need the openspec CLI installed; the tool runs status and instructions commands, derives the change name, reads dependency outputs, and writes artifacts to schema-defined output paths.

Can I use a custom kebab-case change name when scaffolding an OpenSpec workspace?

Yes, you can supply a custom kebab-case change name when scaffolding an OpenSpec workspace, or the tool can derive the change name automatically from your input description.

What happens when required context is missing during change artifact creation?

When required context is missing during change artifact creation, the tool prompts for user clarification to resolve ambiguous input while maintaining momentum toward implementation readiness.

What's the best way to fast-forward artifact creation until requirements are apply-ready?

The best way to fast-forward artifact creation is to provide your change intent, allowing the tool to query build order, generate dependencies sequentially, and progress until apply-ready requirements are satisfied.