openspec-ff-change

Scaffold all OpenSpec implementation change artifacts in one command.

9|4|Updated Jun 13, 2023
One-click install
npx skills add https://github.com/lbrlabs/pulumi-lbrlabs-eks --skill openspec-ff-change-lbrlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/lbrlabs/pulumi-lbrlabs-eks/tree/main/.codex/skills/openspec-ff-change
Command: npx skills add https://github.com/lbrlabs/pulumi-lbrlabs-eks --skill openspec-ff-change-lbrlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fast-forward through OpenSpec artifact creation - generate everything needed to start implementation in one go.

Core Features & Use Cases

  • Single-shot artifact creation: scaffolds all required artifacts for an implementation change.
  • Dependency-aware sequencing: honors artifact dependencies and orders creation correctly.
  • CLI-guided workflow: integrates with the openspec CLI to manage status and instructions.

Quick Start

Describe your desired change in plain language and run openspec new change <name> to scaffold the change.

Frequently Asked Questions about openspec-ff-change

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

FAQPage Schema
How do I generate all OpenSpec artifacts for an implementation change at once?

To generate OpenSpec artifacts in one go, describe your desired change in plain language and run the openspec new change command. This scaffolds all required, ready-to-edit implementation files simultaneously.

What is the best way to speed up OpenSpec artifact creation?

The best way to speed up OpenSpec artifact creation is using a single-shot scaffolding workflow that respects artifact dependencies. This approach outputs all necessary, ready-to-implement files without manual, step-by-step creation.

Can I use the openspec CLI to manage change status and instructions automatically?

Yes, you can use the openspec CLI to manage change status and instructions. The CLI-guided workflow integrates directly with the artifact generation process to enforce correct dependency sequencing.

Does OpenSpec scaffolding respect artifact dependencies during single-shot creation?

Yes, OpenSpec scaffolding respects artifact dependencies during single-shot creation. It honors dependency-aware sequencing to order file creation correctly, ensuring accurate implementation readiness across dependencies.

Why should I use single-shot artifact generation instead of step-by-step OpenSpec creation?

You should use single-shot artifact generation to enable quick iterations across dependencies without manual, step-by-step file creation. It provides a complete, ready-to-implement change package formatted per the template.