spx-apply

Automate OpenSpec change tasks with CLI-driven edits and milestone verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts OpenSpec changes or conversation-driven plans into concrete, tracked code modifications and verification steps so engineers can implement tasks reliably without manual orchestration.

Core Features & Use Cases

  • Change & Plan Modes: Detects and operates on named openspec changes or direct conversation plans and chooses the appropriate workflow.
  • CLI-driven Context: Uses the openspec CLI to read status, apply instructions, and load context files before editing the codebase.
  • Task-by-task Implementation: Implements each pending task with focused edits and marks task checkboxes immediately upon completion.
  • Milestone Verification & PVP: Enforces milestone gates and runs selective parallel verifiers (spx-verifier, spx-arch-verifier, spx-uiux-verifier, spx-test-verifier) with an auto-fix loop and verify-fixes.md logging.
  • Guardrails & Pause Conditions: Pauses on ambiguous tasks, blockers, or design issues and requires explicit user permission to continue after ending the command.

Quick Start

Start implementing the change named fix-auth-bug using the openspec CLI from the project root.

Frequently Asked Questions about spx-apply

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

FAQPage Schema
How do I automate OpenSpec change implementation and task tracking?

Automate OpenSpec change implementation by using the openspec CLI to read status and instructions, applying task-by-task code edits, and immediately marking task checkboxes complete upon finishing each edit.

How does milestone verification work with parallel verifiers for codebase changes?

Milestone verification enforces milestone gates by running selective parallel verifiers like spx-test-verifier and spx-uiux-verifier, executing an auto-fix loop, and logging results into verify-fixes.md.

Can I use this workflow for direct conversation plans instead of named OpenSpec changes?

Yes, the workflow detects and operates on either named OpenSpec changes or direct conversation plans, automatically choosing the appropriate developer workflow to modify the codebase.

Do I need to run the OpenSpec CLI from a specific directory to implement changes?

Yes, you must operate from the repository root directory, invoking the openspec CLI from there to ensure proper loading of context files and application of codebase modifications.

When should I expect the automated implementation workflow to pause and require permission?

The workflow pauses on ambiguous tasks, blockers, or design issues, requiring explicit user permission to continue after the command ends to prevent unintended code changes.

What is the best way to handle verification failures during OpenSpec task implementation?

Handle verification failures through the built-in auto-fix loop which runs selective parallel verifiers, applies fixes automatically, and logs the verification status into verify-fixes.md.