openspec-ff-change

Generate all OpenSpec artifacts for a new change using templates.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/ishibata91/ai-translation-engine-2 --skill openspec-ff-change-ishibata91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-ff-change
Source: https://github.com/ishibata91/ai-translation-engine-2/tree/main/.agent/skills/openspec-ff-change
Command: npx skills add https://github.com/ishibata91/ai-translation-engine-2 --skill openspec-ff-change-ishibata91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to automatically scaffold all OpenSpec artifacts needed for implementation in a single run, eliminating repetitive, multi-step setup and ensuring consistency across changes.

Core Features & Use Cases

  • Scaffold all required artifacts in one invocation based on a change name
  • Enforce workspace prerequisites and proper change setup to prevent misconfigurations
  • Interactive prompts guide users when inputs are unclear to maintain momentum
  • Manage artifact dependencies to ensure an apply-ready state and deterministic builds

Quick Start

Describe the change you want to work on and let OpenSpec generate all artifacts in one go.

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 artifact generation for a new change?

Automating OpenSpec artifact generation involves running a single command that scaffolds all required artifacts for a new change. The tool enforces workspace prerequisites, resolves dependencies in order, and writes files using templates to ensure consistency.

What is the best way to scaffold change management artifacts consistently across projects?

Scaffolding change management artifacts consistently is achieved by using an automated CLI tool that enforces workspace prerequisites and applies standardized templates. This ensures deterministic builds and eliminates repetitive, multi-step manual setup across different projects.

Do I need to configure my workspace before scaffolding OpenSpec artifacts?

Yes, you need a properly configured workspace before scaffolding OpenSpec artifacts. The tool enforces workspace prerequisites and proper change setup to prevent misconfigurations and ensure the generated artifacts are in an apply-ready state.

Can I use interactive prompts to guide artifact generation when inputs are unclear?

Yes, interactive prompts guide users during artifact generation when inputs are unclear. This feature maintains development momentum by requesting necessary information on the fly instead of failing the scaffolding process or requiring a restart.

How does dependency resolution work when scaffolding multiple OpenSpec artifacts?

Dependency resolution during OpenSpec scaffolding works by automatically resolving artifact dependencies in the correct order. This ensures that all generated files respect template constraints and reach an apply-ready state for deterministic builds.

When should I avoid using automated scaffolding for OpenSpec changes?

You should avoid automated scaffolding when your development workflow does not rely on OpenSpec or standardized templates. If your project requires highly customized, non-deterministic artifact structures that bypass workspace prerequisites, manual creation is preferred.