spx-ff

Create openspec-compliant change artifacts with dependency-aware task generation.

9|9|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/nullmastermind/viber-router --skill spx-ff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spx-ff
Source: https://github.com/nullmastermind/viber-router/tree/main/.claude/skills/spx-ff
Command: npx skills add https://github.com/nullmastermind/viber-router --skill spx-ff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts vague or partial change requests into a fully specified, dependency-aware openspec change with all artifacts needed for implementation, removing manual coordination and guesswork for engineers and product teams.

Core Features & Use Cases

  • Focused exploration: Asks 1-3 targeted clarifying questions and inspects the codebase only until sufficient clarity is reached, avoiding open-ended brainstorming.
  • Dependency-aware artifact creation: Derives a kebab-case change name, creates the change via openspec, reads artifact instructions, honors dependencies, and generates files in the required order while using TodoWrite to track progress.
  • Guardrails & compliance: Enforces explicit subagent briefing, prohibits background subagents, annotates high-risk tasks with verify points, and instructs running openspec and bash commands from the project root.
  • Use cases: Adding a new auth flow, implementing an API endpoint with migrations, or producing UI + backend artifacts for a feature rollout.

Quick Start

Create a new change named add-user-auth to implement JWT authentication with refresh tokens stored in Redis.

Frequently Asked Questions about spx-ff

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

FAQPage Schema
How do I generate implementation-ready artifacts for an openspec change request?

To generate implementation-ready artifacts for an openspec change request, this Skill orchestrates openspec workflows to derive a change name, read artifact instructions, and output templates, annotated tasks, and a compliant change structure.

What is the best way to manage dependencies when creating openspec change files?

Dependency-aware artifact creation is managed by reading artifact instructions, honoring declared dependencies, and generating files in the required order while tracking progress with TodoWrite.

How does this Skill handle vague feature requests during artifact generation?

Vague feature requests are resolved through focused exploration, asking 1-3 targeted clarifying questions and inspecting the codebase only until sufficient clarity is reached, avoiding open-ended brainstorming.

Can I use this for repository-level infrastructure updates and bug fixes?

Yes, you can use this for repository-level change workflows including infrastructure updates, bug fixes, and feature rollouts where openspec is used to manage change artifacts.

Does openspec change generation support guardrails for high-risk implementation tasks?

Guardrails are enforced by annotating high-risk tasks with explicit verify points, prohibiting background subagents, and instructing that openspec and bash commands run from the project root.

Why are explicit subagent briefings required during openspec artifact creation?

Explicit subagent briefings are required as a compliance guardrail to ensure focused execution and prevent unmonitored background processes during the generation of change artifacts.