From archcore
Displays Archcore commands for documentation capture, feature planning, decisions, standards, reviews, and multi-document flows with usage guide. Use for onboarding or exploring available skills.
npx claudepluginhub archcore-ai/plugin --plugin archcoreThis skill uses the workspace's default tool permissions.
Guide to what you can do with the Archcore plugin.
Detects repo scale (small/medium/large) and seeds tailored .archcore/ docs: stack rules, run guides, entry-point inventories (medium+), domain maps (large+). For first-time onboarding.
Creates Architecture Decision Records (ADRs) and documentation for architectural decisions, API changes, features, and codebase context that future engineers need.
Share bugs, ideas, or general feedback.
Guide to what you can do with the Archcore plugin.
No routing needed. Single behavior: present the command guide.
Present the following guide:
Most users start here. Describe what you need — the system picks the right document types automatically.
| Command | What it does |
|---|---|
/archcore:capture [topic] | Document a module, component, or topic |
/archcore:plan [feature] | Plan a feature end-to-end (idea → PRD → plan) |
/archcore:decide [topic] | Record a technical decision |
/archcore:standard [topic] | Establish a team standard (decision → rule → guide) |
/archcore:review | Dashboard of document counts and stats; --deep for a full health audit |
/archcore:actualize | Detect stale docs and suggest updates |
Tip: You can also just describe what you need in natural language. Claude will pick the right command automatically.
For users who know which documentation flow they need:
| Command | Flow |
|---|---|
/archcore:product-track [topic] | idea → PRD → plan |
/archcore:sources-track [topic] | MRD → BRD → URD |
/archcore:iso-track [topic] | BRS → StRS → SyRS → SRS |
/archcore:architecture-track [topic] | ADR → spec → plan |
/archcore:standard-track [topic] | ADR → rule → guide |
/archcore:feature-track [topic] | PRD → spec → plan → task-type |
Create a specific document type directly. These commands are user-only shortcuts (the model routes through Quick Start commands for natural-language requests).
Knowledge: /archcore:adr, /archcore:rfc, /archcore:rule, /archcore:guide, /archcore:doc, /archcore:spec
Vision: /archcore:prd, /archcore:idea
Experience: /archcore:task-type, /archcore:cpat
Seven document types are not shown in / autocomplete to reduce cognitive load: mrd, brd, urd, brs, strs, syrs, srs. The model still knows about them and will reach them when you invoke the right track:
mrd / brd / urd): use /archcore:sources-track [topic]brs → strs → syrs → srs): use /archcore:iso-track [topic]mcp__archcore__create_document tool with type=<slug>.If Archcore commands fail with MCP tool errors, the CLI needs to be installed:
curl -fsSL https://archcore.ai/install.sh | basharchcore initThe plugin provides skills, agents, and hooks — but document operations (create, update, delete) require the Archcore CLI, which runs the MCP server.
The guide above, presented as-is. No additional commentary needed.