Qsivs-config

Configure per-stage SIVS engine routing with model and effort overrides.

6|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/inho-team/qe-framework --skill qsivs-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Qsivs-config
Source: https://github.com/inho-team/qe-framework/tree/main/skills/Qsivs-config
Command: npx skills add https://github.com/inho-team/qe-framework --skill qsivs-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams manage and tailor the SIVS routing logic across stages (spec, implement, verify, supervise) by allowing quick changes to the engine, model, and effort overrides, ensuring predictable routing behavior.

Core Features & Use Cases

  • View and edit per-stage routing: set engine (claude/codex), per-stage model overrides, and effort settings.
  • Legacy support and migration: migrate from legacy svs-config to new sivs-config path with detection and guidance.
  • Validation and safety: validates input, warns if codex plugin not installed, and preserves verification gates.

Quick Start

Configure the current stage routing by specifying the stage and engine, for example set implement codex --effort high.

Frequently Asked Questions about Qsivs-config

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

FAQPage Schema
How do I configure per-stage engine routing for deterministic execution?

Per-stage engine routing is configured by specifying the stage and engine, such as setting the implement stage to codex with an optional effort override. This ensures predictable routing behavior across the spec, implement, verify, and supervise stages.

Can I set model overrides and effort levels for individual workflow stages?

Yes, you can apply per-stage model overrides and effort settings to tailor routing logic. This allows quick changes to engine configurations while ensuring deterministic execution for each specific workflow stage.

How do I migrate from legacy svs-config to the new sivs-config path?

Migration from legacy svs-config to the new sivs-config path is supported through automated detection and guidance. The tool validates inputs and enforces configuration rules to ensure a safe transition without breaking existing routing logic.

What happens to verification gates if I switch engines to codex?

Mandatory verification gates are preserved regardless of the engine selections you make. The configuration tool validates inputs and enforces safety rules to ensure verification stages are never bypassed during engine or model overrides.

Do I need the codex plugin installed to use codex engine routing?

The codex plugin must be installed to use codex engine routing safely. The configuration tool provides safety warnings and validates inputs to alert you if the required codex plugin is not detected in your environment.

What is the best way to manage SIVS engine routing across multiple stages?

The best way to manage SIVS engine routing is by using per-stage engine assignments with optional model and effort overrides. This approach validates configuration rules and ensures deterministic execution across spec, implement, verify, and supervise stages.