Adr check

Skill quantum-box/agent-packages/plugins/quantum-box/skills/adr-check

Distribution repository for agent skills and plugins

Install

npx -y skills add quantum-box/agent-packages --skill adr-check

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create or verify Tachyon Architecture Decision Records. Use proactively when: (1) the user asks for ADR, (2) a DD or task makes a long-lived architecture decision, (3) a provider/runtime/security/deployment rule is accepted or rejected, or (4) existing ADR consistency must be checked.

SKILL.md

2.2 KB, as published. Nobody here has run it

ADR Check

Purpose

Use ADRs for durable decisions and constraints. ADRs explain why a direction was chosen, which alternatives were rejected, and what future work must respect. They are not implementation logs.

When To Create

Create or update an ADR for:

architectural constraints or platform-wide rules
provider/runtime selection
deployment, secret, auth, billing, or observability policy
cross-context ownership and boundary decisions
explicit adoption or rejection of a meaningful alternative

Do not create an ADR for:

a local implementation detail with no lasting consequence
a task checklist or verification note
a decision already covered by an existing ADR

Location And Numbering

ADR files live in:

docs/src/architecture/decisions/ADR-xxxx-short-slug.md

Before assigning a number:

git fetch origin main
find docs/src/architecture/decisions -maxdepth 1 -name 'ADR-*.md' | sort
git ls-tree -r --name-only origin/main docs/src/architecture/decisions | grep 'ADR-'

Choose the next number greater than both local and origin/main ADR numbers to avoid collisions when main has moved.

ADR Shape

Use this structure unless a nearby ADR has a stronger local convention:

# ADR-xxxx: Title

## Status

Proposed or Accepted (YYYY-MM-DD)

## Context

## Decision

## Consequences

## Alternatives Considered

## References

Workflow

Search existing ADRs for the same decision.
If a matching ADR exists, update or reference it instead of creating a duplicate.
Allocate the next ADR number from local plus origin/main.
Write the ADR without secrets or environment-specific credential values.
Link the ADR from the related taskdoc and DD.
Update docs/SUMMARY.md if the ADR should be reader-facing.

Output

Report:

ADR path and number source
status
related taskdoc / DD
alternatives captured
follow-up constraints