Help us improve
Share bugs, ideas, or general feedback.
From ideate
Capture an Architecture Decision Record (ADR) for a design choice, tool selection, retirement, or process change. Prompts for context, options considered, decision, and consequences. Stores to Neurons vault at Architecture/ADRs/. Use when making a significant technical decision, retiring a tool, choosing between approaches, or documenting why something was NOT done. Trigger phrases: "architecture decision", "adr", "document this decision", "record this decision", "why we chose", "ideate:adr".
npx claudepluginhub cosmicdreams/claude-plugins --plugin ideateHow this skill is triggered — by the user, by Claude, or both
Slash command
/ideate:adrThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Capture a lightweight ADR and store it permanently to the Neurons vault.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Explores codebases via GitNexus: discover repos, query execution flows, trace processes, inspect symbol callers/callees, and review architecture.
Share bugs, ideas, or general feedback.
Capture a lightweight ADR and store it permanently to the Neurons vault.
If not supplied in $ARGUMENTS, ask the user for the following fields. Gather all before writing — do not write a partial ADR.
| Field | Description | Example |
|---|---|---|
title | Short decision title | "Use Skills over MCPs for non-persistent tools" |
status | Current status | proposed, accepted, superseded, or deprecated |
context | What problem or situation prompted this decision? | "MCP tools load into context on every session..." |
options | What alternatives were considered? | Option A: MCP server. Option B: Skill. |
decision | What was decided and why? | "Use Skills — zero token cost until invoked" |
consequences | What are the results and tradeoffs? | "+ lower token cost — manual invocation required" |
supersedes | (Optional) Title or path of an ADR this replaces | "Use MCP for all integrations" |
If the user provides partial info in $ARGUMENTS, extract what you can and ask only for what's missing.
date +%Y-%m-%d
Slug rules: lowercase title, spaces → hyphens, strip special characters, max 50 chars.
Example: "Use Skills over MCPs for non-persistent tools" → use-skills-over-mcps
---
title: {title}
date: {YYYY-MM-DD}
status: {status}
{supersedes: {old-adr-title} ← include this line only if supersedes was provided, otherwise omit}
---
# {title}
## Status
{Status} — {YYYY-MM-DD}
## Context
{context}
## Options Considered
{options — formatted as a list, with brief pros/cons per option}
## Decision
{decision}
## Consequences
{consequences — call out positives (+) and negatives (-) explicitly}
Read obsidian-rules.md from the workflow plugin references
(~/.claude/plugins/cache/local/workflow/*/references/obsidian-rules.md) to confirm
correct placement. Default path: Architecture/ADRs/{YYYY-MM-DD}-{slug}.md
VAULT_ROOT="$HOME/Vaults/${OBSIDIAN_VAULT_NAME:-Neurons}"
ADR_PATH="Architecture/ADRs/{YYYY-MM-DD}-{slug}.md"
mkdir -p "$VAULT_ROOT/Architecture/ADRs"
cat > "$VAULT_ROOT/$ADR_PATH" << 'EOF'
<formatted ADR content>
EOF
Report: ADR saved: $VAULT_ROOT/$ADR_PATH
On any failure: output the formatted ADR directly in the conversation so it is not lost, then report the error.
Tell the user:
supersedes was set: offer to fetch the old ADR from the vault and update its status to superseded with a link to the new one