openspec-ff-change

Generate OpenSpec artifacts from a descriptive input using the openspec CLI.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/chuangkevin/project-bridge --skill openspec-ff-change-chuangkevin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/chuangkevin/project-bridge/tree/main/.gemini/skills/openspec-ff-change
Command: npx skills add https://github.com/chuangkevin/project-bridge --skill openspec-ff-change-chuangkevin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of all OpenSpec artifacts required to move a change from concept to implementation, eliminating repetitive manual steps and ensuring artifacts are produced in the correct dependency order.

Core Features & Use Cases

  • Rapid scaffold creation: Creates a change scaffold with the openspec CLI and generates required artifacts until the change is apply-ready.
  • Dependency-aware artifact generation: Queries openspec status and instructions in JSON, resolves dependencies, reads completed artifacts for context, and writes new artifact files following schema templates and rules.
  • Interactive clarification and progress tracking: Uses open-ended user prompts when context is unclear and records progress using a TodoWrite tool; ideal for accelerating feature additions like "add-user-auth" or "checkout-flow" changes.

Quick Start

Ask the assistant to fast-forward a change by giving a change name or a short description and instruct it to generate every required OpenSpec artifact until the change is ready 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 generate OpenSpec change artifacts automatically?

The Skill automates OpenSpec artifact generation by parsing openspec status JSON, resolving dependencies, and writing files in order using the openspec CLI to move a change from design to implementation.

What is the best way to scaffold an OpenSpec change from a single description?

Scaffolding an OpenSpec change from a single description is done by giving the assistant a change name, which then queries openspec status, resolves dependencies, and writes required artifact files sequentially without manual intervention.

Does OpenSpec artifact generation handle dependency resolution between files?

Yes, OpenSpec artifact generation handles dependency resolution by parsing openspec status and instructions in JSON, reading completed artifacts for context, and writing new files following schema templates and rules in the correct order.

Can I use the openspec CLI to fast-forward a change to implementation readiness?

You can use the openspec CLI to fast-forward a change to implementation readiness by instructing the assistant to generate every required OpenSpec artifact, tracking progress with TodoWrite, and prompting only when context is unclear.

When should I use automated scaffolding for OpenSpec changes?

Use automated scaffolding for OpenSpec changes when you need to eliminate repetitive manual steps and ensure artifacts are produced in the correct dependency order for a smooth transition from concept to implementation.