adrs-management

Generate formal ADRs from potential ADRs

Identify potential ADRs for specific modules based on the codebase mapping (Phase 2)

Detect and create bidirectional relationships between existing ADRs with clickable links

Create a modular codebase mapping to prepare for ADR identification (Phase 1)

Use this agent when you need to analyze a codebase to understand its architecture and generate Architecture Decision Records (ADRs). This is a two-phase process: Phase 1 - Codebase Mapping: <example> Context: User wants to start analyzing their codebase for ADR generation. user: "I need to understand the architecture of this project and create ADRs for it" assistant: "I'll use the adr-analyzer agent to begin the codebase mapping phase, which will analyze the project structure and create the initial mapping document." <Task tool call to adr-analyzer agent> </example> <example> Context: User has a large legacy codebase without documentation. user: "Can you help me document the architectural decisions in this codebase?" assistant: "Let me use the adr-analyzer agent to first map out the codebase structure and identify the technologies and architectural patterns used." <Task tool call to adr-analyzer agent> </example> Phase 2 - ADR Identification: <example> Context: The mapping.md file has been created with modular structure and user wants to proceed with ADR identification. user: "The mapping is complete, now identify potential ADRs for the AUTH and API modules" assistant: "I'll use the adr-analyzer agent to analyze the AUTH and API modules from the mapping and identify potential ADRs for these specific areas." <Task tool call to adr-analyzer agent> </example> <example> Context: User has a large codebase (5000+ files) and wants to analyze incrementally. user: "Start identifying ADRs, but do it module by module to avoid overwhelming the context" assistant: "I'll use the adr-analyzer agent to read the mapping and present the available modules, then we can analyze them systematically one or two at a time." <Task tool call to adr-analyzer agent> </example> <example> Context: User wants to continue ADR analysis from where they left off. user: "Continue the ADR analysis. We already did AUTH and API, let's do DATA and PAYMENT next" assistant: "I'll use the adr-analyzer agent to analyze the DATA and PAYMENT modules and append the findings to the existing potential_adrs.md." <Task tool call to adr-analyzer agent> </example> <example> Context: User is working on improving project documentation after initial development. user: "We've built this system over the past year but never documented our architectural decisions. Can you help?" assistant: "I'll use the adr-analyzer agent to analyze your codebase systematically. We'll start with mapping the architecture into logical modules, then identify key decisions module by module to keep analysis manageable." <Task tool call to adr-analyzer agent> </example>

Generate a formal ADR from a single potential ADR file identified in the codebase. This agent processes ONE file at a time. When multiple files need processing, the command launcher invokes multiple instances of this agent in parallel.

Detect and create bidirectional relationships between existing ADRs with clickable Markdown links. Analyzes temporal evolution, technical dependencies, semantic similarity, and explicit hints to build a comprehensive ADR relationship graph.