Architecture Decision Records

What it does

This skill enables AI agents to generate, manage, and retrieve Architecture Decision Records (ADRs) to document significant technical choices made during software development. It ensures that the rationale behind decisions is preserved alongside the implementation details for future reference.

When to use it

• Documenting a shift from monolithic architecture to microservices with clear justification.
• Recording security protocol changes required by new compliance regulations.
• Capturing trade-offs between performance optimization and code maintainability.
• Onboarding new team members by providing context on why specific legacy patterns exist.

Key capabilities

• Generates structured ADRs containing the decision status, context, consequences, and implementation details.
• Maintains a centralized repository of architectural history within the project workspace.
• Supports versioning and updating of decisions as requirements evolve over time.
• Formats output to align with standard ADR templates for consistency.

Example prompts

• "Create an Architecture Decision Record for migrating our database from SQL to NoSQL, including the pros and cons we considered."
• "Review our existing ADRs and suggest updates based on recent feedback regarding system scalability."
• "Generate a template for documenting a new authentication strategy and fill it with placeholder details for my team to complete."

Tips & gotchas

Ensure you provide sufficient context about current constraints and business goals when requesting an ADR, as the skill relies on this input to generate accurate rationales. While the tool structures the documentation effectively, human review is still recommended to validate technical feasibility before finalizing decisions.