Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From claude-rag
Lists architectural decisions auto-detected from past conversations chronologically by project, date, choice, and rationale. Supports detailing specific decisions via event ID.
How this command is triggered — by the user, by Claude, or both
Slash command
/claude-rag:decisionsThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Decision Journal List architectural decisions: "$ARGUMENTS" 1. Use `decisions` to fetch auto-tagged decisions from past AI outputs 2. If the user asks about a specific decision, use `detail` with the event ID to get full context Present decisions chronologically with project, date, and a summary of what was decided and why.
List architectural decisions: "$ARGUMENTS"
decisions to fetch auto-tagged decisions from past AI outputsdetail with the event ID to get full contextPresent decisions chronologically with project, date, and a summary of what was decided and why.
npx claudepluginhub thisisyoyodev/claude-plugins --plugin claude-rag/decisionsPre-batches strategic decisions for a feature by scanning plan.md, mining decision candidates, asking the user via AskUserQuestion, and writing decision-sheet.md with a locked Pre-Batched Decisions section in plan.md.
/decisionsQueries project conventions, architectural decisions, and design patterns with source references. Supports topic search and --verbose, --diff flags.