Developer Tools Demo
Dev Hub fix workflow with coverage gate.
Provider adapters generated from one source.
Canonical asset model for commands and workflows.
Approval gates before implementation and release actions.
The Problem Before
Provider lock-in
Assets often work only for one assistant and cannot move cleanly across teams.
Unclear ownership
Feedback arrives without enough context to triage, prioritize, or release.
Manual drift
Repeated copies diverge when commands, agents, and docs are maintained separately.
The Solution
Canonical assets live once under assets, then adapters generate Claude, Codex, Gemini, and open-source outputs.
Interactive
JSON produces evidence that feeds the provider-neutral workflow, adapter generation, and release readiness checks.
Branch produces evidence that feeds the provider-neutral workflow, adapter generation, and release readiness checks.
Test produces evidence that feeds the provider-neutral workflow, adapter generation, and release readiness checks.
Fix produces evidence that feeds the provider-neutral workflow, adapter generation, and release readiness checks.
PR produces evidence that feeds the provider-neutral workflow, adapter generation, and release readiness checks.