openspec-ff-change

Generates all OpenSpec change artifacts in one pass using the openspec CLI.

1|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/trutoman/Conjuros --skill openspec-ff-change-trutoman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/trutoman/Conjuros/tree/main/.opencode/skills/openspec-ff-change
Command: npx skills add https://github.com/trutoman/Conjuros --skill openspec-ff-change-trutoman

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 that process by generating every artifact needed for implementation in a single run, resolving dependencies automatically. ## Core Features & Use Cases - Batch artifact creation: Runs openspec new change, then walks the dependency graph from openspec status --json to create every artifact the apply phase transitively requires. - Instruction-driven generation: Pulls per-artifact templates, rules, and context via openspec instructions and writes each file to its resolved output path. - Store-aware operation: Detects named OpenSpec stores with openspec store list --json and passes --store <id> to all relevant commands. - Use Case: You describe a feature like "add user authentication"; the Skill derives the kebab-case name add-user-auth, scaffolds the change, and produces the proposal, specs, design, and tasks files ready for implementation. ## Quick Start Ask the assistant to fast-forward an OpenSpec change, for example: create all artifacts for a change named add-user-auth so I can start 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 create all OpenSpec change artifacts at once?

Provide a change name or a description of what you want to build. The Skill runs openspec new change, reads the dependency graph from openspec status --json, and creates every artifact the apply phase requires in dependency order.

How does the OpenSpec fast-forward skill handle artifact dependencies?

It parses the requires edges from openspec status --json and walks them transitively from applyRequires, creating artifacts with no pending dependencies first. It re-checks status after each creation since completing one artifact can unblock others.

Does this skill work with named OpenSpec stores?

Yes. If you name a store, it runs openspec store list --json to discover registered store ids and passes --store <id> to commands that read or write specs and changes. Without a store, commands act on the nearest local openspec root.

When are OpenSpec artifacts skipped during fast-forward creation?

An artifact is skipped only when status reports it as skipped due to skip_specs in .openspec.yaml, or when its own instruction field marks it conditional, such as design.md in spec-driven schemas. The Skill never skips artifacts by its own judgment.

What do I need installed to use the OpenSpec fast-forward skill?

You need the openspec CLI installed and available in your environment. The Skill invokes commands like openspec new change, status, instructions, and store list through Bash, so the CLI must be on the PATH.