Adr skills

Domain Modeling

mattpocock

Refine your project's domain model actively.

Architecture Decision Records

wshobson

Document and manage your architectural decisions effectively.

Architectural Decision Record

github

Streamline your architectural decision documentation process.

ADR Creator

tech-leads-club

Document architectural decisions for future clarity.

Architecture Decision Records

anthropics

Document and evaluate architecture decisions effectively.

Architecture Decision Records

sickn33

Capture and manage architectural decisions effectively.

Architecture Decision Records

affaan-m

Capture architectural decisions during coding sessions.

Create and maintain Architecture Decision Records (ADRs) optimized for agentic coding workflows. Use when you need to propose, write, update, accept/reject, deprecate, or supersede an ADR; bootstrap an adr folder and index; consult existing ADRs before implementing changes; or enforce ADR conventions. This skill uses Socratic questioning to capture intent before drafting, and validates output against an agent-readiness checklist.

Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.

Docs-anchored grilling session — challenges a plan against the project's existing language (CONTEXT.md) and recorded decisions (docs/adr/), and updates those files inline as terminology and decisions crystallise. Use when user wants to stress-test a plan against documented domain language, or mentions "grill with docs".

Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.