openspec-ff-change

Generates all OpenSpec change artifacts in dependency order for implementation readiness.

Updated Jun 25, 2026
One-click install
npx skills add https://github.com/ismaelsoilet/ismaelsoilet-landing --skill openspec-ff-change-ismaelsoilet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/ismaelsoilet/ismaelsoilet-landing/tree/main/.cursor/skills/openspec-ff-change
Command: npx skills add https://github.com/ismaelsoilet/ismaelsoilet-landing --skill openspec-ff-change-ismaelsoilet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating OpenSpec change artifacts one by one is slow and error-prone, especially when artifacts depend on each other. This Skill fast-forwards the process by generating every artifact required for implementation in a single guided run. ## Core Features & Use Cases - Batch Artifact Generation: Creates the full required artifact set (proposal, specs, design, tasks) by walking the transitive dependency graph from openspec status --json. - Dependency-Aware Ordering: Reads completed dependency artifacts from disk before writing each new artifact, ensuring consistent context across the change. - Store-Aware Operation: Supports named OpenSpec stores via openspec store list --json and the --store flag for multi-repo workflows. - Use Case: A developer describes a new feature like "add user authentication"; the Skill derives the kebab-case name, scaffolds the change, and produces every artifact needed so implementation can start immediately. ## Quick Start Ask the assistant to fast-forward an OpenSpec change by describing what you want to build, for example requesting it to create all artifacts for adding user authentication.

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 all OpenSpec change artifacts at once?▼

Provide a change name or a description of what you want to build, and the Skill runs openspec new change, then loops through the required artifacts in dependency order using openspec status and openspec instructions until every required artifact exists.

What is the difference between fast-forward and step-by-step OpenSpec artifact creation?▼

Fast-forward generates the entire required artifact set in one run by walking the transitive requires edges from the status JSON. Step-by-step creation has you invoke instructions and write each artifact individually.

Does openspec-ff-change work with named OpenSpec stores?▼

Yes. If the user names a store, the Skill runs openspec store list --json to discover registered store ids and passes --store <id> to commands that read or write specs and changes.

Why does an artifact show done but its dependencies are missing?▼

OpenSpec status is file-existence only, so writing tasks.md early marks tasks done even if specs was never written. The Skill uses each artifact's requires edges, not its status, to determine the full required set.

When does the Skill skip creating an artifact?▼

An artifact is skipped only when its status reports skipped (the change declares skip_specs) or when its own instruction field marks it conditional, such as design.md being optional in spec-driven schemas.