Skip to content

transitrix/transitrix

v0.1.0MIT

Scaffold a Transitrix enterprise-architecture-as-text repository and author your first notation file with inline canonical validation. Drops the canonical zoned canon/ + field/ + codex/ layout with an assistant-neutral AGENTS.md guide and a pinned transitrix.yaml manifest, then walks the user through one of the 12 diagram views (BPMN, DGCA / DGA, Goals, Capability map, Process landscape map, Process Blueprint, Action schedule, Nested blocks, Applications, Integration map, Products, Action Card) + PlantUML rendering, one of the 6 report views (Scenarios, Actions tree, Compliance Impact, Coverage Metric, Rules in Force, Glossary), or a document view (MRD, SRS, SDD) or a codex artefact.

GitHubOpen Website

Transitrix plugin for Claude Code

Transitrix is a text-native methodology for enterprise architecture: every artefact lives in a versioned YAML file, reviewed as a diff, and governed by a published spec. This plugin brings the methodology's operational surface into Claude Code — scaffolding adopter repositories, turning organisational documents into structured canon candidates, running a read-only repo health check, and producing reproducible compliance reports.

Install command (once the plugin is published):

/plugin install transitrix

Self-hosted install (available now — the transitrix/methodology repository acts as a marketplace):

/plugin marketplace add transitrix/methodology
/plugin install transitrix@transitrix-methodology

Other agent hosts: this directory also carries plugin.json, a manifest conforming to the Agent Plugins Specification v1.0.0 — the open, vendor-neutral packaging format six agent-tool vendors published in August 2026. Any client that implements that specification discovers this plugin's skills directly from skills/ per the spec's fixed-location discovery rule; consult that client's own documentation for how it loads a plugin directory or repository. plugin.json is generated from the Claude Code manifest above (.claude-plugin/plugin.json, scripts/generate-plugin-manifests.mjs) so the two never disagree on name or version.

What it produces

Real output, not a mockup — each image below is rendered from this repository's own worked examples (notations/examples/) by @transitrix/diagrams, the same shared rendering library that draws these notations in Studio and in DSM. Every notation the plugin's onboard skill can scaffold has a real renderer in that library; this gallery shows only the subset that renders as a static image today (a diagram view, not an HTML fragment or a data report). A view with no example here is a view this plugin does not yet turn into a picture — nothing below is drawn by hand.

GoalsDGCA/DGA
Goals treeDGCA chain
Capability mapNested blocks
Capability map treeNested blocks

Process Blueprint

Process Blueprint

Action schedule

Action schedule network view

Regenerate with node packages/plugin-examples/src/generate.mjs; CI (.github/workflows/plugin-examples-drift.yml) regenerates on every PR touching the sources and fails the build if the committed images differ by a single byte.

Skills

SkillInvocationWhat it doesMin methodology version
Onboard/transitrix:onboardScaffolds a new adopter repository (zoned canon/ + field/ + codex/ layout, assistant-neutral AGENTS.md, transitrix.yaml manifest) and walks through a first notation file0.5.0
Ingest/transitrix:ingestTurns raw organisational documents — interviews, policies, org charts — into field-zone artefacts and typed canon candidates, then stages a human review queue0.6.0
Repo-check/transitrix:repo-checkRead-only health check: methodology version, coverage-profile resolution, per-TYPE element counts, and integrity flags — all data-free, safe to share externally0.6.0
Report/transitrix:reportProduces a reproducible compliance report (obligation × subject impact matrix or per-regime coverage metric) via a committed view-config artefact and the @transitrix/cli renderer0.6.0
Reg-intel/transitrix:reg-intelMonitors regulatory sources, classifies new instruments against the organisation's obligation catalogue, and stages a review digest for human triage0.6.0
ADR/transitrix:adrRuns a Context/Decision/Consequences interview and lands the result as a gated Architecture Decision Record (operations/decisions/ADR-YYYY-MM-DD-*.md), never self-accepting and never editing an accepted record's body0.6.0
Feedback/transitrix:feedbackRoutes a methodology-directed finding away from data/model problems, runs a scrub-gated interview, and lands it as an anonymised FB-NNNN entry in operations/feedback.md; exports a ready-to-send message on request only, never transmits it itself2.1.0

Prerequisites

  • Claude Code — the plugin runs inside a Claude Code session.
  • An adopter repository — a repository following the Transitrix zoned layout (canon/ + field/ + codex/). Create one with /transitrix:onboard, or clone the worked example at github.com/transitrix/acme-corp.
  • Methodology version pin — the repository must declare its methodology version in transitrix.yaml. Skills check the declared version against their min_version field and warn if the repo is on an older release.
  • Transitrix Studio / CLI (optional) — the ingest and report skills delegate deterministic work to @transitrix/ingest-cli and @transitrix/cli respectively. Both skills run a pre-check (Step 0) and tell the user to install the CLI if it is absent; they do not hand-roll the logic.

What the plugin does not do

  • It does not vendor a copy of the methodology canon. When a skill needs the full spec it fetches it from github.com/transitrix/methodology via WebFetch.
  • It never writes admitted canon directly. Admission stays a deliberate human gate (admitted_by field). The ingest skill emits candidates and a review queue; the human decides what to promote.
  • It does not run in the background or send data to external services beyond github.com/transitrix/methodology.

Methodology

Full specification, notation reference, and migration guides: github.com/transitrix/methodology.

License

MIT — see LICENSE in the methodology repository.