/help
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.
$ npx -y skills add archcore-ai/plugin --skill help --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/help
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
SKILL.md
help.SKILL.mdname: 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."
/archcore:help
Guide to what you can do with the Archcore plugin.
When to use
- "What can I do with Archcore?"
- "Help"
- "What commands are available?"
Routing table
No routing needed. Single behavior: present the command guide.
Execution
Present the following guide:
---
Commands
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.
Plan tracks (`--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>`.
Decide continuations
After `/archcore:decide` creates an ADR, it can extend the chain:
- **Standard cascade** (rule + guide) when the decision is enforceable.
- **Architecture cascade** (spec + plan) when the decision needs a formal technical contract.
You can also explicitly request: *"and make it a standard"* or *"and formalize the contract"*.
Direct document creation
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:
- Market / business / user requirements (`mrd` / `brd` / `urd`) → `/archcore:plan --track sources`
- ISO 29148 cascade (`brs` → `strs` → `syrs` → `srs`) → `/archcore:plan --track iso`
- Any type directly → `mcp__archcore__create_document(type=<slug>)`
Setup
If Archcore commands fail with MCP tool errors, the CLI needs to be installed:
1. **Install CLI:** `curl -fsSL https://archcore.ai/install.sh | bash` 2. **Initialize project:** `archcore init` 3. **Restart** the session
The plugin provides skills, agents, and hooks — but document operations (create, update, delete) require the Archcore CLI, which runs the MCP server.
---
Result
The guide above, presented as-is. No additional commentary needed.
Read more
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."
/archcore:help
Guide to what you can do with the Archcore plugin.
When to use
- "What can I do with Archcore?"
- "Help"
- "What commands are available?"
Routing table
No routing needed. Single behavior: present the command guide.
Execution
Present the following guide:
---
Commands
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.
Plan tracks (`--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>`.
Decide continuations
After `/archcore:decide` creates an ADR, it can extend the chain:
- **Standard cascade** (rule + guide) when the decision is enforceable.
- **Architecture cascade** (spec + plan) when the decision needs a formal technical contract.
You can also explicitly request: *"and make it a standard"* or *"and formalize the contract"*.
Direct document creation
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:
- Market / business / user requirements (`mrd` / `brd` / `urd`) → `/archcore:plan --track sources`
- ISO 29148 cascade (`brs` → `strs` → `syrs` → `srs`) → `/archcore:plan --track iso`
- Any type directly → `mcp__archcore__create_document(type=<slug>)`
Setup
If Archcore commands fail with MCP tool errors, the CLI needs to be installed:
1. **Install CLI:** `curl -fsSL https://archcore.ai/install.sh | bash` 2. **Initialize project:** `archcore init` 3. **Restart** the session
The plugin provides skills, agents, and hooks — but document operations (create, update, delete) require the Archcore CLI, which runs the MCP server.
---
Result
The guide above, presented as-is. No additional commentary needed.
Make your AI code like it already knows your repo. Archcore gives coding agents the architecture, rules, and prior decisions of this repo — so new changes land where your project says they belong and follow the team's conventions, automatically.
Repo: archcore-ai/plugin
Other skills on archcore-ai-plugin.
- /audit
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.
Open skill - /capture
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.
Open skill - /context
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
Open skill - /decide
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.
Open skill - /init
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
Open skill - /plan
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
Open skill