Skills
Plugin
A skill is a slash-command-backed unit of expertise that the agent loads on demand. Each one carries focused knowledge — when to use a document type, required sections, typical relations, common mistakes — so you describe intent instead of schema.
The plugin ships 32 skills in three families:
| Family | Count | What it does | Invoke via |
|---|---|---|---|
| Intent commands | 8 | Route a fuzzy intent to the right document type or workflow | /archcore:capture, /archcore:plan, … |
| Document-type skills | 18 | Create and link one document type with the right template | /archcore:adr, /archcore:prd, … |
| Tracks | 6 | Orchestrate multi-document flows with automatic relation wiring | /archcore:product-track, /archcore:iso-track, … |
Plus one utility: /archcore:verify for plugin integrity checks.
How skills activate
Section titled “How skills activate”- You type a slash command (
/archcore:adr) or describe an intent (“record a decision about caching”). - The host matches the request to a skill definition in the plugin package.
- The skill is loaded into the conversation — its description, guardrails, and relation rules become part of the agent’s working context.
- The agent executes the skill, calling MCP tools as needed.
Every skill ultimately resolves to MCP tool calls. The plugin never writes to .archcore/ directly.
When to use which family
Section titled “When to use which family”- Start with an intent command when you’re not sure which document type fits.
/archcore:captureand/archcore:decidewill pick for you. - Jump to a document-type skill when you know what you’re creating.
/archcore:adr,/archcore:rule,/archcore:spec. - Use a track when one document alone won’t do the job. Need a decision and a rule and a how-to guide? Use
/archcore:standard-track.
Skill catalogue
Section titled “Skill catalogue”See the dedicated pages for each family:
- Intent commands — the 8 routing commands.
- Tracks — the 6 multi-step workflows.
- Document types — the 18 types each
/archcore:<type>skill creates.
For a single-page summary of everything, see the Plugin Skills Reference.
Discovering skills at runtime
Section titled “Discovering skills at runtime”Inside any plugin-enabled session:
/archcore:helpReturns the list of available skills, grouped by family, with one-line descriptions. Useful when you forget the exact command name.
Next steps
Section titled “Next steps”- Intent commands — start here for most asks.
- Tracks — when one document isn’t enough.
- Built-in agents — the two agents that back skills for complex flows.