skills.rest
GQAdonis
GQAdonisCOMMUNITY
Explore all skills by this author →
Website𝕏@gqadonisctoGitHub

kbd-execute

Coordinate KBD execution by selecting backends and recording canonical state.

Updated Mar 27, 2026
Search Tags:#workflow#dispatch#state-management#orchestrator#execute#backend-selection#kbd
One-click install
npx skills add https://github.com/GQAdonis/turboquant-rs --skill kbd-execute
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kbd-execute
Source: https://github.com/GQAdonis/turboquant-rs/tree/main/.opencode/skills/kbd-process-orchestrator/skills/kbd-execute
Command: npx skills add https://github.com/GQAdonis/turboquant-rs --skill kbd-execute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This phase orchestrator enables selecting the best execution backend for a KBD phase, recording canonical state, dispatching work, and preserving KBD as the single source of truth across tools.

Core Features & Use Cases

  • Backend selection across openspec, native-tool, hybrid, and manual backends to enable flexible execution strategies.
  • Execution dispatch: write execution.md and dispatch the phase with a defined contract to the chosen backend.
  • State synchronization: refreshes current-waypoint.json so tools can resume cleanly and stay in sync with KBD.

Quick Start

Follow the execute protocol to select a backend, write the execution plan to execution.md, and dispatch the phase while refreshing waypoint state.

Frequently Asked Questions about kbd-execute

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

FAQPage Schema
How do I coordinate multi-backend execution for a workflow phase?▼

Multi-backend execution coordination is handled by selecting an appropriate backend, writing an execution plan to execution.md, and dispatching the phase while refreshing waypoint state to maintain consistent progress across tools.

What is the best way to keep state-management synchronized when dispatching work across different execution backends?▼

State synchronization across backends is maintained by refreshing current-waypoint.json during execution dispatch, ensuring tools can resume cleanly and stay in sync with the canonical progress.json file as the authoritative source of truth.

How do I select an execution backend for an OpenSpec-backed workflow?▼

Backend selection for an OpenSpec-backed workflow evaluates openspec, native-tool, hybrid, and manual backends, applying execution dispatch logic to choose the strategy that best fits the phase requirements and traceability needs.

Can I use manual execution as a backend option for KBD phase dispatch?▼

Manual backend execution is supported as a valid selection option alongside openspec, native-tool, and hybrid backends, allowing flexible execution strategies when automated dispatch is not required or unavailable.

Why does my workflow lose traceability when switching between execution tools?▼

Traceability is lost when canonical execution state is not recorded properly; initializing progress.json and refreshing current-waypoint.json during dispatch preserves KBD as the single source of truth across tool switches.

What does an orchestrator need to initialize before dispatching a KBD phase?▼

Before dispatching a KBD phase, the orchestrator must load the execution plan, select the backend, write execution.md, and initialize progress.json to ensure traceability and consistent phase progress across tools.

Related Skills

Explore More Software Engineering Skills→
TienchingTienching
3

ralph-init

Generate a canonical PRD and initialize Ralph progress tracking.

Community
Intermediate
tincoppertincopper
10

trellis-continue

Resume an in-progress Trellis task by identifying the current workflow phase and next action.

Community
Advanced
rock-hurock-hu

openspec-continue-change

Generate the next OpenSpec artifact for an active change.

Community
Intermediate
chrisxue90chrisxue90
2

ralph-init

Generate a canonical PRD and initialize a Ralph progress ledger.

Community
Advanced