openspec-ff-change

Generate OpenSpec change artifacts in dependency order with progress tracking.

47|2|Updated Oct 30, 2023
One-click install
npx skills add https://github.com/runtime-env/runtime-env --skill openspec-ff-change-runtime-env
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/runtime-env/runtime-env/tree/main/.gemini/skills/openspec-ff-change
Command: npx skills add https://github.com/runtime-env/runtime-env --skill openspec-ff-change-runtime-env

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill speeds up creating all artifacts needed for an OpenSpec change, letting you skip step-by-step generation and move directly to implementation.

Core Features & Use Cases

  • Fast scaffolding of a new OpenSpec change and its artifacts.
  • Dependency-aware artifact creation: artifacts are generated in the correct order based on their dependencies.
  • Progress tracking and guidance until all required artifacts are completed.

Quick Start

Run the OpenSpec CLI to create a new change scaffold, then check the artifact order with status in JSON. For example, create a change named 'openspec-change'. Next, run openspec status --change 'openspec-change' --json to view dependencies and artifacts. Use openspec instructions <artifact-id> --change 'openspec-change' --json to generate each artifact in dependency order, and report progress until all required artifacts are done. Finally, run openspec status --change 'openspec-change' to verify all apply-required artifacts are complete.

Frequently Asked Questions about openspec-ff-change

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

FAQPage Schema
How do I automate OpenSpec change artifact generation?

Automating OpenSpec change artifact generation involves deriving a kebab-case change name and scaffolding artifacts in dependency order. The workflow tracks progress until all required artifacts are complete, skipping manual step-by-step creation to accelerate implementation.

How does dependency resolution work for OpenSpec artifacts?

Dependency resolution for OpenSpec artifacts operates by sequencing generation based on predefined template constraints. The system checks dependencies for each artifact, ensuring they are generated in the correct order and tracking completion until all apply-required artifacts are done.

What is the best way to track OpenSpec change progress?

Tracking OpenSpec change progress is done by running the CLI status command in JSON mode to view dependencies and artifacts. This reports the current state of each artifact, guiding generation in dependency order until all required artifacts are completed.

Can I generate all OpenSpec change artifacts at once instead of step-by-step?

Generating all OpenSpec change artifacts at once is supported through fast scaffolding. The workflow derives a change name, generates artifacts in dependency order using CLI instructions, and tracks progress, allowing you to skip manual step-by-step generation and move directly to implementation.

Do I need to manually sequence artifact creation in OpenSpec?

Manually sequencing artifact creation in OpenSpec is unnecessary because the workflow uses dependency-aware generation. It automatically follows dependency-driven sequencing and context constraints, ensuring artifacts are generated in the correct order without manual intervention.