records for architecture decision

    1

    Standardize technical decision-making with structured Architecture Decision Records (ADR) and trade-off templates.

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    records for architecture decision

    Example session with this skill installed

    We need to choose between Redis and Memcached for our session storage. The team knows Redis better but Memcached is already in our AWS stack. Write a standard ADR for this.

    • Read your context and instructions
    • Compiled the records for architecture

    I have generated a standard ADR-0006 following the MADR format to document the session storage decision.

    ADR-0006: Use Redis for Session Storage

    StatusAccepted
    Date2024-05-22
    DecidersEngineering Lead, DevOps Lead

    Context

    We need a high-performance distributed cache to store user session data for our web application. The application is deployed on AWS and requires sub-millisecond latency to prevent bottle-necking the request pipeline.

    Decision Drivers

    • Persistence: Ability to recover session data after a node restart.
    • Data Structures: Support for complex session objects beyond simple strings.
    • Team Expertise: Reducing time-to-market by using familiar tools.
    • Infrastructure: Cost and maintenance overhead in AWS.

    Considered Options

    • Option 1: Redis (ElastiCache)
      • Pros: Supports rich data types, built-in persistence, team has high proficiency.
      • Cons: Slightly higher memory overhead compared to Memcached.
    • Option 2: Memcached (ElastiCache)
      • Pros: Simplest architecture, multi-threaded performance, already in use by the legacy stack.
      • Cons: No native persistence, limited to simple key-value pairs, requires team retraining for advanced usage.

    Decision

    We will use Redis 7.x via AWS ElastiCache.

    Rationale

    Redis provides the necessary persistence to ensure users aren't logged out during cache maintenance. While Memcached is already present in our stack, the team's deep experience with Redis outweighs the minor overhead of managing a second ElastiCache cluster.

    Consequences

    • Positive: Fast session lookups, reliable failover, and support for future caching use cases.
    • Negative: Additional cost for a dedicated Redis cluster.
    • Risks: Potential for cache stampede if not configured with proper TTLs.

    Next steps

    1. Initialize the Redis cluster in the staging environment.
    2. Update the express-session configuration to use connect-redis.
    3. Add ADR-0006 to the docs/adr/README.md index.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Technical debt grows when the "why" behind architecture disappears. This skill enforces structural documentation for technical choices, ensuring every major decision is backed by context, trade-offs, and clear consequences. It eliminates the ambiguity of historical codebases by providing standardized templates for recording architectural evolution.

    What it does

    • Standardized Templating provides multiple formats including MADR, Y-Statements, and Lightweight ADRs for varying project needs.
    • Lifecycle Management tracks decisions through states like Proposed, Accepted, Deprecated, and Superseded.
    • Trade-off Analysis structures the comparison of options with explicit pros, cons, and risk mitigation strategies.
    • Migration Planning generates structured deprecation records that include backfill phases and validation steps.
    • Organizational Indexing maintains a central directory and README index to keep decision history searchable.

    How it works

    1. Identify a significant technical change such as a new framework adoption or API design pattern.
    2. Select the appropriate template format based on the complexity of the decision.
    3. Document the context, considered options, rationale, and specific consequences.
    4. Execute the review process using the built-in checklist for senior engineer and stakeholder alignment.

    Frameworks & tools

    This skill utilizes Markdown for documentation, adr-tools for CLI automation, and integrates with standard Git workflows for peer review and version control.

    Why this beats prompting it yourself

    Generic prompts often miss the critical "Consequences" section or fail to distinguish between implementation details and architectural decisions. This skill applies specific industry patterns like Nygard ADRs and MADR, ensuring your documentation remains audit-ready and useful for long-term maintenance.

    Use cases

    • Documenting the selection of a primary database or messaging queue.
    • Recording the rationale for moving from a monolith to microservices.
    • Establishing frontend framework standards during a project kickoff.
    • Deprecating legacy infrastructure in favor of modern cloud-native solutions.

    Known limitations

    Requires manual updates to the status of older ADRs when they are superseded. Does not integrate directly with project management software tickets.

    Manual status updates required when decisions are superseded. No direct integration with JIRA/Linear. Best suited for Git-based workflows.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 8 days ago

    Permissions

    Terminal / Shell
    Write Files
    Listed8 days ago

    What's inside

    Frequently Asked Questions

    This skill provides a structured framework to document the "why" behind technical choices, preventing knowledge loss and technical debt by tracking context, trade-offs, and consequences in a standardized format.

    The skill includes multiple industry-standard templates such as Nygard, MADR, and Y-Statements, along with automated indexing tools and a structured review checklist for senior alignment.

    This skill is designed to work with any AI agent that has file system access and supports Markdown, and it integrates seamlessly into Git-based workflows for version control and peer review.

    When a new architecture choice replaces an old one, the skill provides a specific workflow to mark the original record as "Superseded" and link it to the new "Accepted" record, maintaining a clear audit trail.

    While the skill excels at generating and structuring the records, you will need to manually update the status of older ADRs in your repository when they are replaced to ensure the index remains accurate.

    New in Business & Operations