The Archcore plugin lands on the Claude Code and Cursor marketplaces. The CLI remains the engine that exposes document tools and validates .archcore/; the plugin is the IDE surface that makes those tools first-class inside your agent.
Highlights
- 18
/archcore:*slash commands — 11 intent commands (/archcore:context,capture,decide,standard,plan,review,actualize,status,graph,bootstrap,help), 6 multi-document tracks (product-track,architecture-track,standard-track,feature-track,sources-track,iso-track), andverify - 2 sub-agents —
archcore-assistant(multi-document writer with full MCP access) andarchcore-auditor(read-only documentation health reviewer) - 4 lifecycle hooks — auto-load
.archcore/index on session start, block direct writes to.archcore/files, warn before edits drift from documented context, validate cascade staleness after MCP mutations - 17 document types pre-registered — PRDs, ADRs, RFCs, rules, guides, specs, plans, task-types, code patterns, and the full ISO 29148 cascade (BRS / StRS / SyRS / SRS)
- Bundled CLI — auto-downloaded on first use; respects an existing
archcoreonPATH; honorsARCHCORE_BINandARCHCORE_SKIP_DOWNLOADfor offline / pinned setups - Always-on context rules — every agent session starts already knowing the document model and the MCP-only write rule
Meet the plugin
The CLI does the work. archcore mcp exposes the document tools, archcore validate lints the cascade, archcore init scaffolds a fresh .archcore/. The plugin is the surface that turns those tools into commands you type and guardrails you don’t have to think about. Agents pick up the right context the moment a session opens, and they can’t accidentally clobber .archcore/ files because every write is routed through MCP. Install instructions live at /plugin/.