菜单
Record and retrieve Architecture Decision Records — log a decision's context, options, rationale, and tradeoffs, then list/search them. Use when making a non-trivial design or architecture decision, choosing between tools/approaches, or asked 'why did we do it this way?'
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Double-model verification gate before declaring a build/research/refactor "done". Runs a fresh Anthropic (Claude) review AND an independent OpenAI/Azure critic against the stated goal + criteria, then reconciles. Use before announcing completion of medium/major builds, refactors, major fixes, research deliverables, frontend work, or trade-decision rigor — and on demand via /verify. Skip for small Q&A and trivial edits.
Queue an external action (Telegram message, shell command, GitHub comment, PR merge, file write) for the user's explicit approval before it runs. Use when you want to take an outward-facing or irreversible action that needs sign-off first.
Run a structured multi-position debate over an analytical question, spawning sub-agents to argue each option and counter confirmation bias. Use when comparing options or tradeoffs — 'which is better', 'should we', 'what's the risk', 'evaluate', 'compare options'.
Ingest documents (URLs, local files, PDFs) into a searchable local knowledge base and query stored knowledge. Use when ingesting or storing documents, searching previously stored knowledge, or building research context.
Collect macro market and economic-calendar data (yfinance + FairEconomy API) into a SQLite DB and generate a formatted macro briefing for Telegram. Use when producing a macro/markets briefing or collecting macro market data.
Watch any URL for meaningful changes — price moves, new releases (semver), hiring signals, content diffs, keyword appear/disappear — and alert. Use when tracking competitors, releases, or job postings, or detecting content changes on a web page.
| name | adr-manager |
| description | Record and retrieve Architecture Decision Records — log a decision's context, options, rationale, and tradeoffs, then list/search them. Use when making a non-trivial design or architecture decision, choosing between tools/approaches, or asked 'why did we do it this way?' |
| category | writing |
| maturity | beta |
| tags | ["adr","decision-records","architecture-decisions","documentation"] |
Use when: making a non-trivial technical decision — choosing between options, committing to an architecture, or accepting a tradeoff. Record it so future sessions don't have to guess.
Trigger: any time you make a design decision, choose between tools/approaches, or the user asks "why did we do it this way?"
node ${ADR_MANAGER_HOME:-$HOME/projects/adr-manager}/adr.cjs new \
--project <project-name> \
--title "Decision title" \
--context "Why this decision was needed" \
--options "option1,option2,option3" \
--decision "chosen-option" \
--rationale "Why this option was chosen" \
--tradeoffs "What we gave up and why it's acceptable"
node ${ADR_MANAGER_HOME:-$HOME/projects/adr-manager}/adr.cjs list --project <name>
node ${ADR_MANAGER_HOME:-$HOME/projects/adr-manager}/adr.cjs list
node ${ADR_MANAGER_HOME:-$HOME/projects/adr-manager}/adr.cjs view ADR-001 --project <name>
node ${ADR_MANAGER_HOME:-$HOME/projects/adr-manager}/adr.cjs search "query"
node ${ADR_MANAGER_HOME:-$HOME/projects/adr-manager}/adr.cjs status ADR-001 Superseded --project <name>
~/projects/<project>/.adr/ADR-NNN-<slug>.md