8 skills found
Format, numbering, and when-to-write criteria for Architecture Decision Records in docs/adr/. Use when recording an architectural decision, when another skill flags a decision as ADR-worthy, or when the user asks to write or review an ADR.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
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.
Capture architectural decisions made during Claude Code sessions as structured ADRs. Auto-detects decision moments, records context, alternatives considered, and rationale. Maintains an ADR log so future developers understand why the codebase is shaped the way it is.
Create an Architectural Decision Record (ADR) document for AI-optimized decision documentation.
Guides SDD artifact implementation for NEW and EXISTING projects. Use for DDD glossary, context map, domain models, ADRs, user stories with acceptance criteria. For existing projects, supports gap analysis, code-to-spec reverse engineering, and phased migration. Triggers on SDD, spec-driven, artifact, glossary, context map, domain vision, ADR, legacy documentation, reverse engineering, existing project documentation, gap analysis.
Use this to create or modify architecture decision records (ADRs)
