Skip to main content

system-understanding

Build a code-grounded implementation plan before coding. Use to trace packet flow, factory boundaries, provider config loading, and exact file-level change scope for a requested integration.

Jump to install

Source facts

Repository
rapidaai/voice-ai
Last source activity
August 20, 2026 at 14:36
Detected SKILL.md language
English
Stars
729
Forks
120

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
4 files

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
system-understanding
description
Build a code-grounded implementation plan before coding. Use to trace packet flow, factory boundaries, provider config loading, and exact file-level change scope for a requested integration.
# System Understanding Skill ## Mission Produce an executable, minimal-risk implementation plan from real code paths before changing feature logic. ## Scope Planning and analysis only. Do not implement production changes in this skill run. ## Mandatory discovery sequence 1. Identify feature lane and factory switch: - telephony: `api/assistant-api/internal/channel/telephony/telephony.go` - stt/tts: `api/assistant-api/internal/transformer/transformer.go` - vad: `api/assistant-api/internal/vad/vad.go` - eos: `api/assistant-api/internal/end_of_speech/end_of_speech.go` - llm: `api/integration-api/internal/caller/caller.go` 2. Trace runtime packet flow in dispatcher: - `api/assistant-api/internal/adapters/internal/dispatch.go` 3. Verify UI/provider config load behavior: - `ui/src/providers/provider.development.json` - `ui/src/providers/provider.production.json` - `ui/src/providers/config-loader.ts` 4. Produce exact edit scope: - provider folder - factory file - optional shared contract files - tests to update ## Output requirements - Requested integration type and inferred defaults. - Transport/signal mode chosen and why. - Exact file list to edit (and explicit out-of-scope file list). - Test and validation command plan. - Risks and rollback path. ## Governed lifecycle - This planning skill owns only the `understand` and `plan` phases from `DEVELOPMENT_PROCESS.md`. - The plan must declare acceptance criteria, non-goals, allowed paths, explicit owners, principles, required tests and commands, risks, and rollback. - A separate `plan-challenger` must review the output; this skill may not approve its own plan or perform implementation. - The coordinator attests the approved plan before any implementation worker starts. ## Validation commands - `rg -n "GetTelephony|GetSpeechToTextTransformer|GetTextToSpeechTransformer|GetEndOfSpeech|GetVAD" api` - `rg -n "GetLargeLanguageCaller|GetEmbeddingCaller|GetRerankingCaller|GetVerifier" api/integration-api` - `rg -n "OnPacket\(|dispatch\(" api/assistant-api/internal/adapters/internal/dispatch.go`
View on GitHub