Skip to main content
Engineering Docs has a first-class Claude Code integration. The plugin ships a complete .claude-plugin/plugin.json manifest at the repository root, meaning it is recognized by Claude Code’s native plugin system out of the box. You can install from the official marketplace with a single slash command, register the GitHub repository manually, or use npx engineering-docs --claude to copy the full plugin tree to your global Claude directory. The fastest path — no cloning, no scripts, no manual configuration.
1

Open Claude Code and run the install command

Claude Code chat
Claude Code fetches the plugin from the official registry and installs it to ~/.claude/plugins/engineering-docs/.
2

Reload your session

Close and reopen your Claude Code session, or run /reload to pick up the new plugin. The 22 skills are now available automatically.

​
Method 2: Manual marketplace registration

Use this method if you want to pin to a specific commit or fork of the repository.
1

Register the marketplace source

Claude Code chat
2

Install from the registered source

Claude Code chat
3

Reload your session

Restart Claude Code or run /reload to activate the newly installed plugin.

​
Method 3: Global flag install via npx

This method copies every plugin file directly to ~/.claude/plugins/engineering-docs/ on your local machine, giving you full offline access to all skills, hooks, agents, and the MCP server config.
1

Run the installer with the Claude flag

terminal
The short alias -c also works:
terminal
2

Verify the install path

The installer prints the full destination path as it runs. Confirm files landed in:
3

Reload Claude Code

Restart Claude Code or run /reload in chat to pick up the new plugin directory.

​
What gets installed

When you use the --claude flag (or methods 1 / 2), the following structure is copied to ~/.claude/plugins/engineering-docs/:
The CLAUDE.md agent configuration file is written using safe-write: it is created in the install directory only if it does not already exist there, so any customizations you have made are always preserved.

​
Validate the plugin

Claude Code ships a built-in plugin validator. Run it from inside the plugin directory to confirm the manifest, skills, agents, and hooks all pass validation:
terminal
A successful run prints a green confirmation for each component. This is the same validation the official marketplace runs on submission.

​
Plugin manifest

The .claude-plugin/plugin.json manifest that Claude Code reads:
.claude-plugin/plugin.json

​
SessionStart hook

The plugin registers a SessionStart hook that runs check-progress.js every time a Claude Code session starts (and on clear or compact). The hook scans the current working directory for in-progress documentation and surfaces a summary — so Claude always knows which documents have already been produced before the first message.
hooks/hooks.json
The SessionStart hook means Claude never asks for context that already exists in your project directory. It reads prior documents before asking any clarifying questions, so it will never repeat information you have already provided in a previous session.

​
MCP server

The .mcp.json file configures a local MCP server that exposes three tools Claude can call:
  • validate_document_set — checks all generated documents for structural completeness
  • check_consistency — verifies entity names, roles, and decisions are consistent across documents
  • generate_index — builds the master blueprint index from completed documents
These tools are used automatically by the orchestrator skill (using-engineering-docs) when it runs cross-document consistency checks.