executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
components-and-backendsChoose, configure, and troubleshoot speech-to-speech VAD, STT, LLM, and TTS backends, optional extras, language behavior, prompts, tools, and benchmark safety.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is to choose or debug a VAD, STT, LLM, or TTS
component for speech-to-speech, including optional extras, model/device
choices, Qwen3-TTS modes, direct audio-input LLMs, language behavior, prompts,
tool calls, and benchmark planning.
serve/local/talk, host/port, VAD flags, or session
capacity: route to cli-and-server.--stt, --llm_backend, and --tts.
Defaults are parakeet-tdt, responses-api, and qwen3.scripts/inspect_backend_registry.py.qwentts-cpp-python wheel/runtime match
before diagnosing model code. For Apple Silicon, use the MLX quantization
mapping described in the recipes.--stt none bypasses transcription and forwards the completed VAD audio turn
to an LLM that supports audio input. In this package that means
--llm_backend chat-completions plus an explicitly audio-capable --model_name.
Do not pair --stt none with the default responses-api profile.responses-api and chat-completions share the --responses_api_* connection
flags. They call different upstream endpoints.transformers and mlx-lm tool calling uses prompt-rendered function
signatures and parsed <code>...</code> calls; remote OpenAI-compatible
backends pass tools structurally.--mac-optimal-settings supplies macOS defaults only. Any explicit backend,
model, global device, or component-device flag wins over the preset.