From ork
Provides ADR templates in Nygard format for documenting architectural decisions with sections for context, decision, consequences, and alternatives. Use when recording tech choices, evaluating options, or establishing patterns.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ork:architecture-decision-recordThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
assets/adr-template.mdchecklists/adr-review-checklist.mdexamples/adr-0001-adopt-microservices.mdexamples/adr-0002-choose-postgresql.mdexamples/adr-0003-api-versioning-strategy.mdreferences/adr-best-practices.mdrules/_sections.mdrules/_template.mdrules/interrogation-reliability.mdrules/interrogation-scalability.mdrules/interrogation-security.mdscripts/adr-frontmatter.yamlscripts/adr-manager.pyscripts/create-adr.mdscripts/list-adrs.pytest-cases.jsonArchitecture 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: AI Agent Hub Team
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:
npx claudepluginhub yonatangross/orchestkit --plugin orkDocument architectural decisions using ADR format. Use when making significant architectural choices that affect future development.
Documents significant architectural and technical decisions with context, alternatives, trade-offs, and consequences. Creates a decision trail for teams. Use when choosing technologies, making infrastructure decisions, or establishing standards.
Generates Architecture Decision Records with context, rationale, alternatives, and status lifecycle. Prevents forgotten design rationale.