Dogfood Skill

VCS Provider

This skill uses VCS operations through Exarchos MCP actions (create_issue, etc.). These actions automatically detect and route to the correct VCS provider (GitHub, GitLab, Azure DevOps). No gh/glab/az commands needed — the MCP server handles provider dispatch.

Overview

Retrospective analysis of Exarchos MCP tool usage. Uses the MCP server's own self-service capabilities as the primary diagnostic instrument — describe APIs, views, playbooks, and runbooks turned inward to diagnose failures.

This is the in-runtime, event-sourced counterpart to the older transcript-only triage: agents file friction reports in real time via exarchos_workflow feedback, which land on the shared meta/feedback stream. Dogfood reads that stream as a first-class input (Step 1h) — each feedback.recorded event is an agent-surfaced friction signal already captured at the moment it hurt, not reconstructed after the fact.

Three distinct failure modes require different fixes — code changes, documentation updates, or skill instruction improvements. Mixing them wastes effort.

Platform-Agnosticity

Per docs/designs/archive/2026-03-09-platform-agnosticity.md: the MCP server is the self-sufficient, platform-agnostic core. The debug trace relies entirely on MCP tools — not conversation introspection — so it works for any MCP client. Conversation scanning is supplementary.