pluggable-impl

Implement pluggable transcription providers via a TDD-driven workflow from pre-flight through PR review.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/sujithatzackriya/skills --skill pluggable-impl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pluggable-impl
Source: https://github.com/sujithatzackriya/skills/tree/main/skills/pluggable-impl
Command: npx skills add https://github.com/sujithatzackriya/skills --skill pluggable-impl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It eliminates the uncertainty and churn of implementing new transcription providers by giving a structured, step-by-step workflow that keeps code, docs, tests, and review in sync.

Core Features & Use Cases

  • Repeatable provider implementation flow: turns provider architecture steps into an execution checklist covering pre-flight context, planning, tests-first, implementation, verification, docs, review, commit, and progress logging.
  • TDD with safety and regression gates: enforces test-first development plus build/type verification and a provider-specific self-review aligned to core KPIs.
  • Provider-specific autonomy modes: supports standalone execution with user consent gates and an --sub-skill mode used by /autopilot for autonomous commit/review/merge under stricter orchestrated conditions.
  • Use Case: Add an OpenAI-compatible batch transcription provider (new API adapter + registry wiring + presets/UI if needed) while maintaining stability via RED→GREEN→REVIEW loops and explicit manual test planning.

Quick Start

Use the command: /pluggable-impl openai-compatible to implement the OpenAI-compatible transcription provider step-by-step with tests, review, and progress tracking.

Frequently Asked Questions about pluggable-impl

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

FAQPage Schema
How do I implement a new transcription provider using TDD?▼

To implement a transcription provider using TDD, execute a deterministic workflow spanning pre-flight context, planning, tests-first, implementation, verification, docs, and PR review to keep code, docs, tests, and review in sync.

What is the workflow for adding an OpenAI-compatible STT batch transcription provider?▼

Adding an OpenAI-compatible STT batch provider involves executing a step-by-step flow: pre-flight context, test-first development, API adapter creation, registry wiring, optional UI presets, and verification through RED→GREEN→REVIEW loops.

Can I use an autonomous workflow for integrating streaming transcription providers?▼

Yes, streaming transcription providers can be integrated autonomously using an `--sub-skill` mode under `/autopilot` governance, which orchestrates commit, review, and merge under stricter conditions with user consent gates.

Does implementing model file integrations like .gguf or .onnx require manual test planning?▼

Yes, integrating model files like .gguf or .onnx requires explicit manual test planning alongside build and type verification. The workflow enforces test-first development and provider-specific self-review aligned to core KPIs.

What's the best way to ensure documentation stays in sync when adding Whisper transcription variants?▼

The best way to keep documentation in sync when adding Whisper variants is using a deterministic TDD-driven workflow that satisfies docs-as-truth requirements, integrates PR lifecycle checks, and logs progress continuously.