openspec-ff-change

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

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/javakishore-veleti/lifting-diary-app --skill openspec-ff-change-javakishore-veleti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/javakishore-veleti/lifting-diary-app/tree/main/.qwen/skills/openspec-ff-change
Command: npx skills add https://github.com/javakishore-veleti/lifting-diary-app --skill openspec-ff-change-javakishore-veleti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating an OpenSpec change normally requires stepping through each artifact (proposal, specs, design, tasks) one at a time. This Skill fast-forwards the process by generating every artifact required before implementation in a single workflow, resolving dependencies automatically. ## Core Features & Use Cases - Batch Artifact Creation: Derives the full required artifact set from openspec status --json by transitively walking requires edges, then creates each one in dependency order. - Instruction-Driven Generation: Pulls per-artifact templates, rules, and context via openspec instructions, and delegates to other skills or commands when the instruction field says so. - Store-Aware Operation: Discovers registered OpenSpec stores with openspec store list --json and applies a sticky --store <id> flag across all scoped commands. - Use Case: You describe "add user authentication" and the Skill creates the change scaffold, writes the proposal, specs, design, and tasks files, then reports that everything is ready for /opsx-apply. ## Quick Start Ask the assistant to fast-forward an OpenSpec change by describing what you want to build, for example: create all artifacts for a change named add-user-auth.

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?

Run the fast-forward workflow: it calls openspec new change, reads the dependency graph from openspec status --json, and generates every artifact in the required set in dependency order. You only need to provide a change name or a description of what to build.

What artifacts does an OpenSpec change need before implementation?

The required set comes from applyRequires plus every artifact reachable by following requires edges transitively, typically proposal, specs, design, and tasks. The Skill computes this from openspec status --json rather than assuming a fixed list.

Does openspec-ff-change work with registered OpenSpec stores?

Yes. It runs openspec store list --json to discover registered store ids, then appends --store <id> to all commands that read or write specs and changes. Without a store, commands act on the nearest local openspec/ root.

Can I skip the design or specs artifact in an OpenSpec change?

An artifact is skipped only when status reports it as skipped via skip_specs in .openspec.yaml, or when its own instruction field marks it conditional, such as design.md. The Skill never skips artifacts based on its own judgment.

Why does openspec status show tasks done but specs missing?

Status is file-existence only, so writing tasks.md early marks tasks done even if specs was never created. The Skill uses each artifact's requires edges, not its status, to determine what still needs to be created.