Skip to content
TrustedSkillsbeta
Back to all skills

Architecture Decision Records

Checked
wshobson·vlatest·backend·MIT

This skill generates Architecture Decision Records (ADRs) to document design choices, fostering clarity and collaboration within projects.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add wshobson/agents --skill architecture-decision-records -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

wshobson

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned wshobson/agents at 46891e7e60.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
46891e7e60
Manifest
plugins/documentation-generation/skills/architecture-decision-records/SKILL.md
Scanned
1 file, 420 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The architecture-decision-records skill helps AI agents document and manage architectural decisions made during software development. It provides a structured format for recording the context, options considered, decision rationale, and consequences of each choice, ensuring transparency and traceability in system design.

When to use it

  • When documenting major technical choices in a project for future reference
  • During team collaboration to ensure alignment on architectural decisions
  • As part of a software development lifecycle to maintain an audit trail of design trade-offs

Key capabilities

  • Structured documentation of architectural decisions
  • Recording context, options, rationale, and consequences
  • Facilitating traceability and transparency in system design

Example prompts

  • "Document the decision to use microservices over monolithic architecture for our new application."
  • "Create an architecture decision record for choosing React over Vue.js as our frontend framework."
  • "Generate a template for recording architectural decisions during our sprint planning meeting."

Tips & gotchas

  • Ensure all stakeholders are involved in reviewing and approving decisions before finalizing the records.
  • Maintain consistency in formatting to make records easier to search, review, and update later.