About
This skill empowers development teams to maintain a clear, historical record of significant technical decisions. By utilizing a standardized markdown template and integrating directly with Confluence via MCP tools, it automates the process of identifying decision numbers, documenting context, weighing trade-offs (positive, negative, and neutral), and recording rejected alternatives. It is essential for teams looking to improve architectural transparency, reduce technical debt, and provide future developers with the 'why' behind complex system choices.