Commands Reference
Sooner or later on any engagement you will want to know exactly what Wire ran on your behalf, or you will want to run one step yourself rather than ask for it, and for either of those you need the names. This page is the catalogue of them. Every Wire command follows the pattern /wire:- , and every artifact has three lifecycle commands, generate, validate and review, except where noted in the tables below, so that once you know an artifact's name you can usually work out its commands without looking them up.
Skills Reference
Much of the day-to-day work on an engagement is not a Wire command at all: you are writing a dbt model, fixing a LookML view or working out why a job failed overnight, and what you want is for the conventions Wire encodes to apply to that work without your having to look them up. That is what skills are for. Wire skills are Markdown files that Claude loads as instruction sets, and unlike commands, which you invoke explicitly, most skills auto-activate, which is to say they "fire" when the work you are doing matches their trigger conditions, without you needing to reference them.
MCP Servers
Much of what matters on an engagement happens outside the repository: decisions are taken on client calls, progress is tracked in Jira or Linear and documents are read and commented on in Confluence or Notion, and if Wire could see none of that its record would be a thinner thing. Wire integrates with five MCP (Model Context Protocol) servers to close that gap. All are optional, and Wire works without any of them, but when they are present they add meeting context to reviews, sync artifact status to issue trackers, replicate artifacts to document stores and provide library documentation lookups during development.
FAQ
The questions below are the ones that come up most often, grouped by topic, and where a fuller answer lives elsewhere on this site the answer points you to it.
Troubleshooting
When something goes wrong with Wire it is usually one of a small number of things: the plugin has not loaded, a command cannot find its inputs, dbt will not compile, an integration is not answering or the execution log has been damaged. This page takes each of those in turn, giving the symptom you will see and the steps to work through, and it ends with where to go if none of them helps.
Management Commands
Every engagement needs a certain amount of housekeeping around the artifacts themselvesnew.
Release Notes
Recent release history for the Wire Framework. For full changelog detail from v3.0.0 onwards, see CHANGELOG.md.
Testing Wire Itself
If you are changing Wire itself rather than using it on an engagement, sooner or later you will want to know what stands between a mistaken edit to a spec and that mistake reaching a consultant's machine. This page documents Wire's own automated test suite: how the framework tests itself, not how to test a client's data platform. Every spec change, every new command and every release goes through the same tiered suite described below.