メニュー
ADR templates in the Nygard format with context, decision, consequences, and alternatives. Use when writing ADRs, recording an architectural decision, or evaluating options.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/yonatangross/orchestkit --skill architecture-decision-recordコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
SKILL.md を表示中
| name | architecture-decision-record |
| license | MIT |
| compatibility | Claude Code 2.1.220+. |
| description | ADR templates in the Nygard format with context, decision, consequences, and alternatives. Use when writing ADRs, recording an architectural decision, or evaluating options. |
| version | 2.0.0 |
| author | OrchestKit |
| tags | ["architecture","documentation","decision-making","backend"] |
| context | fork |
| agent | backend-system-architect |
| user-invocable | false |
| complexity | medium |
| persuasion-type | guidance |
| metadata | {"category":"document-asset-creation"} |
| allowed-tools | ["Read","Glob","Grep","WebFetch","WebSearch"] |
Architecture Decision Records (ADRs) are lightweight documents that capture important architectural decisions along with their context and consequences. This skill provides templates, examples, and best practices for creating and maintaining ADRs in your projects.
ADRs serve as architectural memory for your team:
Each ADR should follow this structure:
Format: ADR-####: [Decision Title]
Example: ADR-0001: Adopt Microservices Architecture
Current state of the decision:
What to include:
What to include:
Be specific and actionable:
What to include:
Document at least 2 alternatives:
For each alternative, explain:
Links to relevant resources:
Proposed → Accepted → [Implemented] → (Eventually) Superseded/Deprecated
↓
Rejected
Once accepted, don't edit ADRs. Create new ADRs that supersede old ones.
ADRs are historical records written as if the decision is being made now.
ADRs capture decisions, not implementation details.
Get input from relevant stakeholders before accepting.
Use 4-digit zero-padded numbers: ADR-0001, ADR-0002, etc. Maintain a single sequence even with multiple projects.
Keep ADRs in version control alongside code:
/docs/adr/ or /architecture/decisions//create-adr [number] [title] to generate ADR with auto-filled contextassets/adr-template.mdscripts/create-adr.md - Dynamic ADR generator with auto-filled context
/create-adr [number] [title]$ARGUMENTS and !command for dynamic contextassets/adr-template.md - Static template for manual use
| Rule | Impact | What It Covers |
|---|---|---|
| interrogation-scalability | HIGH | Scale questions, data volume, growth projections |
| interrogation-reliability | HIGH | Data patterns, UX impact, coherence validation |
| interrogation-security | HIGH | Access control, tenant isolation, attack surface |
❌ Too Technical: "We'll use Kubernetes with these 50 YAML configs..." ✅ Right Level: "We'll use Kubernetes for container orchestration because..."
❌ Too Vague: "We'll use a better database" ✅ Specific: "We'll use PostgreSQL 15+ for transactional data because..."
❌ No Alternatives: Only documenting the chosen solution ✅ Comparative: Document why alternatives weren't chosen
❌ Missing Consequences: Only listing benefits ✅ Balanced: Honest about costs and trade-offs
❌ No Context: "We decided to use Redis" ✅ Contextual: "Given our 1M+ concurrent users and sub-50ms latency requirement..."
ork:api-design: Use when designing APIs referenced in ADRsork:database-patterns: Use when ADR involves database choicesSkill Version: 2.0.0 Last Updated: 2026-01-08 Maintained by: OrchestKit
Keywords: adr, architecture decision, decision record, document decision Solves:
Keywords: when to write adr, adr lifecycle, adr workflow, adr process, adr review, quantify impact Solves:
Keywords: tradeoff, pros cons, alternatives, comparison, evaluate options Solves:
Keywords: consequence, impact, risk, benefit, outcome Solves: