NOTE: paste-text fallback works without MCPs, but docs MCPs (Notion, Confluence, Granola) are typically only connected in Cowork — the Cowork variant has better fidelity for MCP-sourced meetings. Fold a meeting transcript or notes into structured intake. Use when user says '/meeting-notes', 'capture meeting notes'…
Executed pre-completion checklist — third sibling of /prospect (before execution) and /retrospect (after shipping). Six checks, three outcomes each (PASS/FAIL/INVALID); an unrun check blocks the verdict. Catches failures that emit no error: a check whose FORM bounds what it finds, and a decision correct in isolation…
Run a structured pre-mortem on a plan or approach BEFORE execution. Per-step risk enforcement, active evidence-sourcing pass (autonomous lookups + targeted user-asks for anything that could become objective), simpler-alternative discipline, plan-formation diagnosis, action verdicts (PROCEED/SHRINK/SPLIT/DEFER/KILL)…
Audit a surface against a checklist to answer 'is it clean/legal/consistent to ship for THIS event?' — the recurring sibling of /foundational-review. Parallel exploration per surface, controller re-verification of every load-bearing claim, then tiered evidence-celled findings and a phased remediation plan (findings…
Read-only orientation — render a scannable table of what just happened so you can situate yourself. Modes: '/recap' (this session), '/recap arc' (the last product arc), '/recap commit' (the last commit), '/recap push' (the last push's commits — what I sent up), '/recap pull' (the last pull's changes — what came down…
Run a structured retrospective on a shipped commit range, release, deployment, PR, commit, or session. Per-fix validation enforcement, active evidence-sourcing pass (autonomous lookups + targeted user-asks for anything that could become objective), simpler-alternative discipline, re-diagnosis, action verdicts, and a…
Render a per-project feature roadmap — a Band×Status grid (Shipped/Current/Next/Later × done/in-progress/blocked/buildable) synthesized from CLAUDE.md + PROGRESS.md, persisted to a committed ROADMAP.md with staleness-aware refresh. Modes: '/roadmap' (nearest project), '/roadmap ' (a projectslist tag), '/roadmap…
Quick lookup into working rules. Use when user says '/rules', '/rules 22', '/rules dependencies', 'look up rule about...', 'what rule covers...', or references a specific rule number. (Code port — ADR-094.).
Configure aria-knowledge plugin. Creates or validates a knowledge folder, checks dependencies, sets audit cadences, and writes config. Run on first install or after plugin updates. Trigger: '/setup', 'setup aria-knowledge', 'configure knowledge'.
Show knowledge base health metrics — file counts, backlog depth, audit status, codemap dates, tag stats, and coverage gaps. Use when user says '/stats', 'knowledge stats', 'how is my knowledge base', 'show stats', 'knowledge health', 'dashboard'. (Code port — ADR-094.).
Install or remove the aria-knowledge status-line meter — a context-window progress bar plus the rolling 5-hour and 7-day plan-usage percentages, shown at the bottom of the Claude Code CLI. Use when the user says '/statusline', 'add a context meter', 'show context usage in the status line', 'show my 5-hour usage'…
NOTE: this skill requires connected docs MCPs with WRITE access (Notion, Confluence, Google Docs), which are typically only present in Cowork — the Code variant exists for parity but most users will want the Cowork variant. Mirror approved decisions from the knowledge folder out to a connected docs MCP (Notion…
Close out a session cleanly when the work is done — no passoff intended. Reviews session work, updates PROGRESS.md / CLAUDE.md / memory, commits changes, captures session knowledge via /extract, and confirms everything is wrapped up, captured, and documented. Use when the task is complete and nothing needs to carry…
ARIA — Applied Reasoning and Insight Architecture. Persistent human-governed knowledge for Claude Code via a five-phase lifecycle: capture → govern → promote → apply → refresh. Stages session insights/decisions/feedback into review backlogs, promotes approved items to a tag-indexed markdown base, and applies them via…
★not rated 17
changed 16d agoA
tokens not measured
Mine your distilled knowledge corpus — memory feedback rows, rules backlogs, always-on indexes — for recurring corrections that deserve promotion to numbered standing rules. Clusters by theme, verifies every quote at its source file, ranks by cross-session recurrence (>=2 distinct sessions), and writes a rule ONLY on…
Knowledge management for Claude Cowork — capture, organize, and apply durable knowledge across your work, available in any project workspace via a persistent folder grant. Companion to aria-knowledge for Claude Code; both share one knowledge folder so insights flow between conversational and engineering work. Default…
ARIA audit skills — /audit dispatcher plus /audit-knowledge, /audit-config, /audit-style, /audit-usage. Use when user says 'audit knowledge', 'audit config', 'audit style', 'audit usage', 'review setup', or runs the slash commands.
ARIA context surfacing — /context and /rules. Use whenever the user asks to load knowledge by topic, references a tag, or asks 'what do we know about X' or 'look up rule N'. Also fires the implicit task-start tag match described in AGENTS.md.
Rule 22 — change decision framework. Apply BEFORE every Edit/Write: emit a [Rule 22] block (Low Impact or High Impact 7-step) ABOVE the tool call in the same turn, then run scripts/aria/record-edit-intent.sh to log intent. Verify scope AFTER each edit.
Command "aria" from mikeprasad/aria-knowledge, covering /aria, common actions and codex notes.
★not rated 17 16d agoA0 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: