A Claude Code plugin for enterprise architecture

Install it

In Claude Code, add the ArcKit marketplace:

/plugin marketplace add tractorjuice/arckit-claude

Then install the plugin from the Discover tab, or from a terminal:

claude plugin install arckit@arckit-claude

Open a project and run /arckit:start. It looks at what the project already has and tells you which command to run next. Getting started has the full steps.

What it writes

Each command writes one document from a template, using what's already in your project. You review it, fix it and sign it off. Every document is Markdown in your repository, with an ID, a version and a status.

That's eight of 76 commands. The rest cover stakeholders, business cases, data models, research, procurement, security and operations. See all commands.

What's in the plugin

• 76 commands, each with its own template and usage guide.
• 38 agents. Research runs in separate agents, so dozens of web pages and documentation searches don't fill your conversation.
• Automatic checks. They run whatever the AI does: they correct file names and numbering, stop keys and passwords being written into documents, and record how each document was made.
• Seven connected sources: AWS, Microsoft and Google Cloud documentation, UK government code, UK public tenders, Data Commons statistics and Trello.
• A parallel build. /arckit:build writes a whole set of documents from a recipe, in dependency order. Read the build guide.

How it differs from documentation plugins

Most architecture plugins for Claude Code read your code and describe what's there: a C4 diagram, an API reference, a decision record for a change you've just made. That's useful, and it starts from the code.

ArcKit starts earlier, with stakeholders, goals and requirements, and carries them through to the design.

• Documents are linked. A decision record names the requirements it answers. A design review checks the design against your principles. The traceability matrix shows what nothing covers yet.
• Documents are controlled. Each one has an ID, a version, an owner, a status and a review date, and starts as a draft.
• Claims cite their sources. When a document draws on a policy, a vendor's submission or a web page, the claim points to it.

The two kinds work together. Use a code-analysis plugin to describe the system you have, and ArcKit to govern the one you're changing.

TOGAF, arc42 and other overlays

The same marketplace holds 19 more plugins. Install only the ones you need.

• Methods: TOGAF ADM (arckit-togaf-adm), arc42 (arckit-arc42) and Open Agile Architecture (arckit-oaa).
• Countries: the EU, France, the Netherlands, Austria, Canada, the UAE, Australia and the USA.
• Sectors: UK NHS clinical safety, UK financial services payments, UK legacy IT and Australian energy.
• AI systems: an overlay for the architecture of AI agents.

The command reference lists every overlay command. UK government teams can start with ArcKit for the UK public sector.

Questions people ask