new

You can document architectural decisions by interactively capturing context, researching options, comparing alternatives, and generating a structured markdown Architectural Decision Record with status, context, rationale, and alternatives.

An Architectural Decision Record (ADR) documents important technical decisions to ensure project clarity and maintainability. Create one when your team decides on technologies, capturing context, options considered, and final rationale.

To write an ADR with alternatives and rationale, this Skill prompts you for decision details, facilitates comparing technical options, and ensures the generated markdown file contains required sections documenting your choices and reasoning.

Yes, you can manage the lifecycle of technical decisions. The Skill supports ADR lifecycle management by ensuring required sections are present and automatically searching existing ADRs and the codebase for relevant contextual information.

The best way to compare technical options is using the Skill's interactive option exploration feature, which helps you evaluate different technical choices like a new database technology and generates a markdown file documenting the final decision.

Creating an ADR does not require manually searching the codebase. The Skill automatically performs contextual research across your codebase and existing ADRs to gather relevant information for the architectural decision documentation.