Engineering Docs supports 10 additional AI coding agents beyond Claude Code, Gemini CLI, and Cursor. Each agent has its own dedicated install flag in scripts/install.js, a matching platform-specific manifest in the integrations/plugins/ directory, and a supported target in both the Bash and PowerShell setup scripts. Use the tabs below to find the exact commands for your agent.
Goose
Pi
OpenCode
Kilo Code
Roo Code
Cline
Factory Droid
Kimi Code
Codex
Copilot CLI
Install path: ~/.config/goose/extensions/engineering-docs/ (global)Alternatively, configure Goose manually by adding a new extension entry in ~/.config/goose/config.yaml and pointing it at the cloned repository.The plugin ships integrations/plugins/.goose/GOOSE.md which contains the complete auto-trigger rule table and behavioral standards. This file is copied as GOOSE.md (safe-write) into the install directory.Setup script: Install path: ~/.pi/packages/engineering-docs/ (global)Or install directly from the git repository using Pi’s native package manager:The plugin ships integrations/plugins/.pi/PI.md which provides Pi with the full auto-trigger rule table and the same behavioral standards used in every other agent integration. The PI.md file is written with safe-write semantics.Setup script: Install path: .opencode/engineering-docs/ (workspace-local)OpenCode uses a workspace-local plugin directory. Run this command from your project root. The plugin manifest at integrations/plugins/.opencode/plugin.json references ./skills/ for skill discovery and AGENTS.md for instructions.Setup script: Install path: ~/.kilo-code/plugins/engineering-docs/ (global)Kilo Code also supports marketplace installation. The plugin manifest at integrations/plugins/.kilo-plugin/plugin.json provides the structured metadata Kilo Code’s marketplace browser reads.Setup script: Install path: ~/.roo-code/plugins/engineering-docs/ (global)Roo Code also supports marketplace installation. The plugin manifest at integrations/plugins/.roo-plugin/plugin.json provides the structured metadata Roo Code’s plugin browser reads.Setup script: Install path: .clinerules (workspace root, single file)Cline uses a single .clinerules file at your project root rather than a directory of skill files. The installer copies integrations/plugins/.cline/.clinerules to the current working directory. This file contains all auto-trigger rules and behavioral standards in one place.This is a workspace-scoped install. Run it in each project where you want Cline to have access to Engineering Docs skills. There is no global install path for Cline.
Install path: ~/.factory/plugins/engineering-docs/ (global)The plugin manifest at integrations/plugins/.factory-plugin/plugin.json provides Factory Droid with the structured metadata it needs to register the plugin. The full plugin tree — including all 22 skills, agents, hooks, and the MCP config — is copied to the global plugins directory.Setup script: Install path: ~/.kimi-code/plugins/engineering-docs/ (global)Short alias: -kYou can also install directly from within Kimi Code using its native plugin command:The Kimi Code manifest at integrations/plugins/.kimi-plugin/plugin.json includes a skillInstructions field that maps Engineering Docs skill calls to Kimi Code’s native tool names (AskUserQuestion, Read, Write, Edit, Bash, etc.) and declares the Interactive, Read, and Write capability flags.Setup script: Install path: .codex/engineering-docs/ (workspace-local)Short alias: -xCodex uses a workspace-local .codex/ directory. Run this from your project root. The plugin manifest at integrations/plugins/.codex-plugin/plugin.json provides structured metadata and lists ./skills/ as the skills directory. Codex can also install from its own marketplace.Setup script: Install path: ~/.copilot/plugins/engineering-docs/ (global)Short alias: -pThe plugin ships integrations/plugins/.copilot/COPILOT.md which provides GitHub Copilot CLI with the complete auto-trigger rule table and behavioral standards. The COPILOT.md file is written using safe-write semantics.Setup script: All install paths at a glance
Setup script target reference
Both cross-platform scripts support all of the targets above. Use the -Target parameter on PowerShell or the --<target> flag on Bash:
All install methods — npx, setup.sh, and setup.ps1 — apply the same safe-write rules. Agent config files (AGENTS.md, GOOSE.md, PI.md, COPILOT.md, etc.) are created only if they do not already exist at the destination. Your existing customizations are always preserved.
After installing
Reload your agent or restart its CLI session to pick up the new plugin directory. Once loaded, trigger the orchestrator skill by telling your agent:
The using-engineering-docs skill activates automatically, detects whether this is a new (Greenfield) or existing (Brownfield) project, and guides you through the full documentation sequence. 