opsx-ff

Scaffold software change artifacts in dependency order under openspec/changes.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/moogah/emacs --skill opsx-ff-moogah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opsx-ff
Source: https://github.com/moogah/emacs/tree/main/.claude/skills/opsx-ff
Command: npx skills add https://github.com/moogah/emacs --skill opsx-ff-moogah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill accelerates the move from concept to implementation by automatically scaffolding the full set of artifacts, guidance, and change directories needed to implement a signal or feature.

Core Features & Use Cases

  • End-to-end artifact scaffolding: creates a scaffolded change at openspec/changes/<name>/ and produces artifacts in dependency order.
  • Guided workflow orchestration: coordinates with openspec, status checks, and TaskCreate to track progress from idea to tested implementation.
  • Guardrails and reuse: enforces dependency awareness, prompts for clarifications when context is unclear, and maintains a safe, iterative path to ready-to-implement changes.

Quick Start

Describe the desired change with /opsx-ff followed by a kebab-case change name to start generating artifacts.

Frequently Asked Questions about opsx-ff

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

FAQPage Schema
How do I automate scaffolding for software changes from idea to artifacts?

Automating software change scaffolding generates a structured change directory and produces implementation artifacts in dependency order. It coordinates workflow orchestration to track progress from the initial idea through tested implementation.

What is dependency-aware sequencing for artifact generation?

Dependency-aware sequencing creates implementation artifacts in a specific order based on their relationships. This ensures each artifact is generated only after its dependencies are satisfied, maintaining a safe and iterative path.

How do I create a scaffolded change directory for a new feature?

Creating a scaffolded change directory involves specifying a kebab-case change name to initialize the pipeline. The system then automatically scaffolds the full set of artifacts, guidance, and directories needed for implementation.

Does the workflow orchestration handle unclear context during artifact generation?

Yes, the workflow orchestration includes guardrails that prompt for clarifications when context is unclear. This enforces dependency awareness and maintains a safe, iterative path to ready-to-implement changes.

Can I use this to track progress from idea to tested implementation?

Yes, you can track progress from idea to tested implementation using guided workflow orchestration. It coordinates with status checks and task creation tools to monitor the entire change pipeline.

What are the limitations of automating change scaffolding with sequential artifact creation?

The approach requires a structured change pipeline and clear context. While guardrails prompt for missing information, highly ambiguous project requirements may stall the automated dependency-aware sequencing process.