About
This skill empowers developers to perform 'decision archaeology' within their codebase by tracing the lineage of ideas, architectures, and patterns. It provides structured frameworks for understanding why specific approaches were adopted, evaluating previously failed attempts with modern context, and detecting when 'new' ideas are actually revivals of past paradigms. By systematically investigating Git history, Architecture Decision Records (ADRs), and legacy documentation, it ensures that technical shifts are driven by informed context rather than architectural fashion, helping teams avoid costly mistakes and preserve institutional knowledge.
