openspec-ff-change

Generate and sequence implementation artifacts for OpenSpec changes.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/lz-freedom/polybull-stock-helper --skill openspec-ff-change-lz-freedom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/lz-freedom/polybull-stock-helper/tree/main/.opencode/skills/openspec-ff-change
Command: npx skills add https://github.com/lz-freedom/polybull-stock-helper --skill openspec-ff-change-lz-freedom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec.

What problem does it solve?

OpenSpec-FF-Change automates the rapid setup of implementation artifacts by generating and sequencing all necessary artifacts in a single operation, removing manual scaffolding and ordering tasks.

Core Features & Use Cases

  • Automatic artifact scaffolding for a change, including dependency-aware generation.
  • Status-driven artifact creation using openspec status to determine ready artifacts.
  • Iterative progress: creates artifacts in dependency order until the change is fully apply-ready.

Quick Start

Use the openspec tool to bootstrap a new change, inspect status, and generate all required artifacts in sequence:

  • openspec new change "<name>"
  • openspec status --change "<name>" --json
  • For each artifact with status "ready", fetch instructions with openspec instructions <artifact-id> --change "<name>" --json and create the artifact using the provided template, then re-check status until all required artifacts are done.
  • Finally, run openspec status --change "<name>" to confirm readiness.

Frequently Asked Questions about openspec-ff-change

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

FAQPage Schema
How do I auto-generate implementation artifacts for a software change?

To auto-generate implementation artifacts for a software change, use OpenSpec to bootstrap the change, inspect its status, and iteratively create structured artifact files in dependency order until fully apply-ready.

What is dependency-aware artifact scaffolding in software development workflows?

Dependency-aware artifact scaffolding automatically sequences and generates interdependent implementation artifacts by reading dependency states, removing the need for manual file creation and ordering tasks during software changes.

How do I sequence multiple interdependent artifacts for instant deployment?

You sequence interdependent artifacts by running openspec status to identify ready items, fetching template instructions for each, creating the artifact files, and re-checking status until all required artifacts are fully generated.

Does OpenSpec require CLI commands to manage change artifacts?

Yes, OpenSpec requires CLI commands to manage change artifacts, utilizing commands like openspec new change to bootstrap, openspec status to check readiness, and openspec instructions to fetch template specifications.

What's the best way to automate change management scaffolding using openspec?

The best way to automate change management scaffolding is using OpenSpec's status-driven generation, which iteratively fetches instructions and produces structured artifact files based on dependency states until the change is apply-ready.

Why does manual artifact creation fail for complex software changes with interdependencies?

Manual artifact creation fails because complex software changes require strict dependency ordering, which OpenSpec resolves by reading dependency states and automatically sequencing artifact generation to satisfy build rules.