Plugin Skills Reference
Plugin
Section titled “/archcore:plan track flows”
Section titled “/archcore:decide continuations”
Section titled “/archcore:audit modes”
Quick lookup of every command shipped with the Archcore Plugin — one page, no clicks. For grouped coverage with examples see Skills. For the document types these commands produce, see Document types.
All 7 commands
Section titled “All 7 commands”| Command | Outcome | Flags |
|---|---|---|
/archcore:init | Make your repo legible to AI agents | --mode=small|medium|large |
/archcore:context | Load what’s already decided before you change code | --git-changes |
/archcore:capture | Document what already lives in code | — |
/archcore:plan | Turn an idea into a scoped implementation plan | --track product|feature|sources|iso |
/archcore:decide | Record a decision and (optionally) make it a team rule | — |
/archcore:audit | Find stale, missing, or drifting docs | --deep, --drift, or any non-flag filter (implies --deep) |
/archcore:help | Navigate the skill catalog | — |
/archcore:plan track flows
Section titled “/archcore:plan track flows”A track is a multi-step cascade. The skill creates each document through MCP in order, wires relations automatically, and pauses for your review before the next step.
--track | Flow | Relations created | Use when |
|---|---|---|---|
product | idea → prd → plan | prd implements idea, plan implements prd | Lightweight product flow — simple, fast, individual features. |
feature | prd → spec → plan → task-type | spec implements prd, plan implements spec, task-type related plan | Full feature lifecycle with formal spec and delivery pattern. |
sources | mrd → brd → urd | brd related mrd, urd related mrd, brd | Discovery — market, business, user research. |
iso | brs → strs → syrs → srs | strs implements brs, urd; syrs implements strs; srs implements syrs | Regulated systems, multi-team projects, full traceability. |
Default (no --track) routes to the product flow.
/archcore:decide continuations
Section titled “/archcore:decide continuations”After an ADR is recorded, /archcore:decide offers a follow-up cascade:
| Continuation | Flow | Relations created | Use when |
|---|---|---|---|
| Standard chain | adr → (optional cpat) → rule → guide | rule implements adr, guide related rule, cpat related rule | The decision is a team standard that needs enforcement. |
| Architecture chain | adr → spec → plan | spec implements adr, plan implements spec | The decision needs formal specification and a plan. |
/archcore:audit modes
Section titled “/archcore:audit modes”| Invocation | Mode | Returns |
|---|---|---|
/archcore:audit | Dashboard (default) | One-screen counts by category, status, type, relation coverage. |
/archcore:audit --deep | Full audit | Gaps, staleness, orphans, missing relations, prioritized fixes. |
/archcore:audit --deep tag:auth | Scoped audit | Same as --deep but scoped to a tag, type, or category. |
/archcore:audit --drift | Staleness scan | Code drift, cascade drift, temporal drift — what’s gone out of date. |
Document types
Section titled “Document types”The 18 document types don’t have dedicated slash commands — commands above route to them. Call mcp__archcore__create_document directly when you need a specific type without a routing command.
| Layer | Types |
|---|---|
| Vision | prd, idea, mrd, brd, urd, brs, strs, syrs, srs, plan |
| Knowledge | adr, rfc, rule, guide, doc, spec |
| Experience | task-type, cpat |
Full descriptions and required sections for each type: Document types.
See also
Section titled “See also”- Skills — full descriptions with examples for every command.
- Document types — required sections per type.