gz-skill-router

name: gz-skill-router persona: main-session description: Route agents to the correct skill for a given task type. Use when starting a session, when unsure which skill applies, or when an agent needs to discover the right workflow for a task. category: agent-operations lifecycle_state: active owner: gzkit-governance last_reviewed: 2026-06-07 metadata: skill-version: "6.1.0" govzero-framework-version: "v6" model: haiku

gz-skill-router

Route agents to the correct gzkit skill based on task type. This is a lookup aid, not an orchestrator — it maps intent to the right workflow entry point.

When to Use

• Starting a new session and unsure which skill applies
• Task description is ambiguous across multiple skill domains
• Onboarding a new agent to gzkit's skill catalog

When NOT to Use

• You already know which skill to invoke
• The task is a simple CLI command (just run it)

Decision Tree

Task arrives
    │
    ├── Exploring a new idea or feature?
    │   ├── Vague idea, needs design dialogue ──────→ gz-design
    │   ├── Ready to define product requirements ───→ gz-prd
    │   └── Ready to record an architecture decision → gz-plan
    │
    ├── Creating or managing ADRs?
    │   ├── Create a new ADR with interview ────────→ gz-adr-create
    │   ├── Promote a pool ADR to canonical ────────→ gz-adr-promote
    │   ├── Evaluate ADR quality (scoring) ─────────→ gz-adr-evaluate
    │   ├── Check ADR lifecycle/OBPI status ────────→ gz-adr-status
    │   ├── Sync ADR governance state (all layers) ─→ gz-adr-sync
    │   ├── Build ADR-to-artifact traceability ─────→ gz-adr-map
    │   └── Emit a receipt event to the ledger ─────→ gz-adr-emit-receipt
    │
    ├── Working on an OBPI?
    │   ├── Decompose ADR into OBPI briefs ─────────→ gz-obpi-specify
    │   ├── Audit plan alignment before coding ─────→ gz-plan-audit
    │   ├── In-flight defect fix (≤10 lines, ≤2 files) → AGENTS.md § Defect-fix routing (direct fix; skip pipeline)
    │   ├── Execute the full implementation pipeline → gz-obpi-pipeline
    │   ├── Claim/release OBPI work locks ──────────→ gz-obpi-lock
    │   ├── Review code quality after implementation → gz-obpi-simplify
    │   └── Reconcile briefs against evidence ──────→ gz-obpi-reconcile
    │
    ├── Auditing or closing out?
    │   ├── Gate 5 audit (COMPLETED → VALIDATED) ───→ gz-adr-audit
    │   ├── Human attestation ceremony ─────────────→ gz-adr-closeout-ceremony
    │   └── GHI-driven patch release ───────────────→ gz-patch-release
    │
    ├── Running checks or validation?
    │   ├── Full quality checks (lint+test+type) ───→ gz-check
    │   ├── Gate compliance for an ADR ─────────────→ gz-gates
    │   ├── Gate 2 implementation verification ─────→ gz-implement
    │   ├── Validate governance artifacts ──────────→ gz-validate
    │   ├── Query artifact relationships ───────────→ gz-state
    │   ├── Report gate/lifecycle status ───────────→ gz-status
    │   └── Audit CLI doc coverage ─────────────────→ gz-cli-audit
    │
    ├── Governance infrastructure?
    │   ├── Initialize gzkit scaffolding ───────────→ gz-init
    │   ├── Create/refresh constitution ────────────→ gz-constitute
    │   ├── Validate config path coherence ─────────→ gz-check-config-paths
    │   └── Record semver migration events ─────────→ gz-migrate-semver
    │
    ├── Agent & repository operations?
    │   ├── Sync skill mirrors and surfaces ────────→ gz-agent-sync
    │   ├── Commit and push with quality gates ─────→ git-sync
    │   ├── Preserve context across sessions ───────→ gz-session-handoff
    │   ├── Run maintenance chores ─────────────────→ gz-chore-runner
    │   └── Repository hygiene and cleanup ─────────→ gz-tidy
    │
    └── Cross-repository?
        └── AirlineOps governance parity scan ──────→ airlineops-parity-scan

Keyword Lookup

Skill Catalog Commands

Use these to discover and scaffold skills directly from the CLI:

# List all active skills in the catalog
uv run gz skill list

# Scaffold a new skill stub under .gzkit/skills/
uv run gz skill new <slug>

Staleness Warning

This router must be updated when skills are added, renamed, or retired. After any skill catalog change, verify this decision tree still covers all active skills. The gz-agent-sync skill should trigger a router review.

Attribution

Routing pattern adapted from using-agent-skills in addyosmani/agent-skills (MIT).

Related

• AGENTS.md § Available Skills (the authoritative catalog)
• gz-agent-sync (triggers after skill changes)