Skills publicadas
Mostrando 12 de 101backlog
View and manage pending backlog items. Use when user says "/aria-cowork:backlog", "/aria-cowork:backlog insights", "/aria-cowork:backlog clear", "what is pending", "show backlogs", "check backlog status". (Cowork variant — namespaced-only.)
aria-knowledge
Generate a passoff package so the next reader can pick up cleanly — for future-you in a new session (typically when context is high and you need to restart) or for a coworker (via brief mode). Default + `auto` modes emit a paste-ready next-session opener as the headline artifact, alongside PROGRESS / CLAUDE / memory updates, commit, and /extract; `brief` mode emits an 80-150 word coworker-facing p
clip-thread
Capture a chat or email thread from a connected MCP to the knowledge intake. Use when user says "/aria-cowork:clip-thread" or "archive this conversation". Pulls thread content from ~~chat (Slack, Teams) or ~~email (Gmail, MS365) MCP into intake/clippings/ for review. (Cowork variant — namespaced-only.)
meeting-notes
Turn meeting notes, transcripts, or connected docs into structured ARIA intake records. Trigger on /meeting-notes, capture meeting notes, process standup, or fold this transcript.
aria-knowledge
Extract uncaptured knowledge from the current conversation before it's lost to compaction. Use after completing a task, before switching context, before large exploratory work (multi-file reads, codebase scans), or when the user signals session end. Trigger: '/extract', 'extract knowledge', 'capture session knowledge'. Also prompt mid-session: 'Task complete — want me to run /extract?' and 'Switch
retrospect
Structured retrospective on a shipped commit range, release, PR, commit, or session: per-fix validation, evidence-sourcing pass, re-diagnosis, action verdicts, growing failure-mode library. Triggers — "/aria-cowork:retrospect", "retrospect this". (Cowork variant — namespaced-only.)
aria-probe
Run a 4-step validation probe for the aria-cowork spec. Tests whether this Cowork plugin can verify cwd, write to the user-attached knowledge folder, read a file pre-placed by aria-knowledge in Code, and capture or fall back gracefully on the transcript surface. Outputs structured results both to the conversation and to a probe-results file. Use when validating the aria-cowork spec before Phase 1
stats
Show knowledge base health metrics — file counts, backlog depth, audit status, tag stats, and coverage gaps. Use when user says "/aria-cowork:stats", "knowledge stats", "how is my knowledge base", "show stats", "knowledge health", "dashboard". (Cowork variant — namespaced-only.)
sync-decisions
Mirror approved ARIA decisions from the knowledge folder to connected docs MCP destinations with explicit external-write review. Trigger on /sync-decisions or sync ADRs to docs.
aria-knowledge
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), and a growing failure-mode pattern library. Triggers: '/prospect' (defaults to pla
daily-audit
First-message audit substitute for Cowork. Use when user says "/daily-audit", "/aria-cowork:daily-audit", "audit check", "daily check", "session start audit", or at the start of a Cowork session to surface audit-cadence status. Cowork has no SessionStart hook (per ADR-004); this skill is the manual equivalent — checks /audit-knowledge +.
stats
Show ARIA knowledge-base health metrics: counts, backlog depth, audit status, codemap freshness, tag coverage, and gaps. Trigger on /stats or knowledge health.