菜单
Show available Archcore commands and how to use them. Use when onboarding, exploring what skills are available, or when you're not sure which command to run.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Audit Archcore docs: dashboard (counts, status, relations, orphans), deep coverage audit, or drift detection (code/cascade/temporal staleness). Use for 'show status', 'documentation gaps', 'check if docs match code', or after a staleness warning. Not for creating docs.
Document a module, component, or system — automatically picks the right type (ADR, spec, doc, or guide). Use when you need comprehensive docs for a codebase element and don't want to choose the document type yourself.
Surface the rules, ADRs, specs, patterns, and reference docs that apply to a code area before changing it — or recap project focus when picking up work. Use for 'what rules apply to X', 'before I touch Y', 'what governs my current changes' (--git-changes), 'pick up where we left off'. With uncommitted changes in play you MAY run --git-changes once per task to load the rules for what you've touched (not per-edit). Not for creating docs, planning, or audits.
Record a decision: finalized → ADR (optionally rule + guide or spec + plan); open proposal → RFC. Use for 'we decided', 'record this decision', 'make it a standard', 'draft an RFC', 'should we switch to Y'. Not for feature planning or documenting existing code.
First-time Archcore setup. Detects repo scale and shape, then composes a full first-day seed — stack rule, run guide, data-model, integrations, config, entry points, public surface, a linked architecture overview, and specs for the top hotspot modules — shown in ONE preview and created on a single confirm. Imports agent-instruction files — aggregate files (CLAUDE.md/AGENTS.md/.cursorrules) as link stubs, modular rule files (.cursor/rules/*.mdc and equivalents) as rule docs by default. Use on a fresh clone, empty `.archcore/`, or 'set up archcore'. Not for individual docs or planning.
Plan a feature or initiative: default product flow (idea → PRD → plan), feature flow with formal spec + task-type, sources flow (MRD → BRD → URD), or ISO 29148 cascade (BRS → StRS → SyRS → SRS). Use for 'plan the X redesign', 'create a roadmap', 'plan a new feature'. Pick a flow with --track. Not for recording a decision — use /archcore:decide.
| name | help |
| description | Show available Archcore commands and how to use them. Use when onboarding, exploring what skills are available, or when you're not sure which command to run. |
Guide to what you can do with the Archcore plugin.
No routing needed. Single behavior: present the command guide.
Present the following guide:
Describe what you need — the agent picks the right skill. Slash commands are shortcuts.
| Command | What it does |
|---|---|
/archcore:init | First-time setup — seed stack rule, run guide, optional imports from CLAUDE.md / AGENTS.md / .cursorrules |
/archcore:context [path, topic, --git-changes] | Surface rules, ADRs, specs, and patterns that apply to a code area (or your --git-changes), or pick up where work left off |
/archcore:capture [topic] | Document a module, component, or topic (picks ADR / spec / doc / guide automatically) |
/archcore:decide [topic] | Record a finalized decision (ADR, optionally codified as rule + guide or formalized as spec + plan) or open proposal (RFC) |
/archcore:plan [feature] | Plan a feature end-to-end. Default flow: idea → PRD → plan. Switch with --track product|feature|sources|iso |
/archcore:audit | Documentation dashboard. --deep for full audit, --drift for code/cascade/temporal staleness |
/archcore:help | Show this guide |
Tip: You can also just describe what you need in natural language. The agent will pick the right command automatically.
--track)| Track | Flow | Use when |
|---|---|---|
product (default) | idea → PRD → plan | Lightweight individual feature or rapid prototyping |
feature | PRD → spec → plan → task-type | Well-scoped feature with formal contract + repeatable pattern |
sources | MRD → BRD → URD | Discovery research: market, business, user inputs |
iso | BRS → StRS → SyRS → SRS | Formal ISO 29148 cascade for regulated systems |
Invoke: /archcore:plan "<topic>" --track <name>.
After /archcore:decide creates an ADR, it can extend the chain:
You can also explicitly request: "and make it a standard" or "and formalize the contract".
There are no per-type slash commands. Create documents through the commands above, or call mcp__archcore__create_document directly when you need exact type-level control:
mrd / brd / urd) → /archcore:plan --track sourcesbrs → strs → syrs → srs) → /archcore:plan --track isomcp__archcore__create_document(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.