openspec-ff-change

Name: openspec-ff-change
Availability: InStock
Author: joannanowakowska

Create OpenSpec change scaffolds and planning artifacts in dependency order.

10|Updated Jul 7, 2026

Search Tags:#planning #cli #change management #openspec #artifact creation

Ready to run

npx skills add https://github.com/joannanowakowska/plannning-poker-app --skill openspec-ff-change-joannanowakowska

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/joannanowakowska/plannning-poker-app/tree/main/.github/skills/openspec-ff-change
Command: npx skills add https://github.com/joannanowakowska/plannning-poker-app --skill openspec-ff-change-joannanowakowska

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of creating a complete OpenSpec change so you do not have to step through each artifact manually.

Core Features & Use Cases

Fast-forward artifact creation: Creates the change scaffold and the required planning artifacts in dependency order.
Dependency-aware workflow: Uses OpenSpec status and instructions to determine which artifacts are ready next.
Interactive clarification: Asks for missing details when the change name or scope is unclear.
Use Case: A product or engineering team wants to quickly prepare an implementation-ready change without manually managing the planning sequence.

Quick Start

Ask the skill to create a new OpenSpec change for your requested feature or fix.

Frequently Asked Questions about openspec-ff-change

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

FAQPage Schema

How do I create an OpenSpec change scaffold with all planning artifacts at once?▼

To create an OpenSpec change scaffold in one pass, this skill generates all required implementation artifacts in dependency order. It prepares a complete, implementation-ready change scaffold instantly without manual sequencing.

What is dependency-aware artifact generation in change management workflows?▼

Dependency-aware artifact generation uses OpenSpec status and instructions to determine which planning artifacts are ready next. It ensures correct sequencing and validates readiness before generating subsequent change artifacts.

Do I need the openspec CLI to generate implementation-ready change artifacts?▼

Yes, generating implementation-ready change artifacts requires the openspec CLI. The skill depends on the CLI to inspect status, apply instructions, and drive the artifact creation workflow in proper dependency order.

Can I use interactive clarification to define an unclear OpenSpec change scope?▼

Yes, interactive clarification asks for missing details when the OpenSpec change name or scope is unclear. It ensures the generated artifact scaffold accurately reflects your requested feature or fix before creation.

Best way to prepare a complete OpenSpec change without manually managing the planning sequence?▼

The best way to prepare a complete OpenSpec change without manual management is using a fast-forward artifact creation workflow. It automatically scaffolds the change and generates planning artifacts in dependency order.

Why does my OpenSpec artifact generation stop before all planning artifacts are created?▼

Artifact generation stops because the dependency-aware workflow checks OpenSpec status and instructions to verify readiness. It halts when prerequisite artifacts are incomplete, ensuring artifacts are only created in valid dependency order.