orch-spx

Coordinate planning, specification, application, verification, and compaction phases in AI coding sessions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This orchestrator removes the need for a human to manually drive multi-phase AI coding sessions by reliably advancing planning, specification, implementation, and verification phases while enforcing strict sequencing and permission rules.

Core Features & Use Cases

  • Phase orchestration: Enforces the prescribed /spx-plan → /spx-ff → /compact → /spx-apply → /spx-verify pipeline and short/verify-only variants.
  • Dispatching & gating: Sends exact action-tag prompts, handles permission approvals or denials, and determines when to wait for human input.
  • Safety & protocol enforcement: Prevents unauthorized modifications, scopes commands precisely, and requires specific context steps before verification.
  • Use Case: Use this Skill to continuously drive a developer-facing agent session from initial request through specification and implementation, ensuring auto-verification and looped fixes until critical issues are resolved.

Quick Start

Send the orchestrator the user's change request verbatim, for example: /spx-plan add dark mode support

Frequently Asked Questions about orch-spx

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

FAQPage Schema
How do I automate multi-phase AI coding workflows for planning and verification?

Automating multi-phase AI coding workflows requires an orchestrator to coordinate planning, specification, application, and verification phases. This skill drives end-to-end openspec workflows, enforcing strict action-tag outputs and phase sequencing rules across agent sessions.

Do I need to manually approve every step during an openspec workflow session?

Manual approval during openspec workflows is only required for specific permission requests. The orchestrator autonomously advances through phases like specification and compaction, automatically pausing solely when human input is necessary to proceed.

How does an autonomous orchestrator handle phase sequencing and safety during code changes?

An autonomous orchestrator handles phase sequencing by enforcing prescribed pipelines like plan, fast-forward, compact, apply, and verify. It maintains safety by scoping commands precisely, preventing unauthorized modifications, and requiring specific context steps before verification.

What is the best way to continuously drive an AI agent session from request to auto-verification?

The best way to continuously drive an AI agent session is using an autonomous orchestrator to loop fixes until critical issues are resolved. Send the user's change request verbatim to initiate the planning, specification, and implementation pipeline.

Can I use this orchestrator for short or verify-only variants of software change tasks?

Yes, you can use this orchestrator for short or verify-only variants of software change tasks. It supports dispatching exact action-tag prompts and gating for these specific variants while maintaining protocol enforcement.

Why does my AI coding session pause unexpectedly during specification and implementation phases?

An AI coding session pauses during specification or implementation phases because the orchestrator determines that human input is required. It enforces strict sequencing rules and only halts when handling permission approvals or denials for safety.