Skills architecture-decision-records
📦

architecture-decision-records

Content revision r2 Safe ⚙️ External commands🌐 Network access

Create Clear Architecture Decision Records

Important technical decisions often lose their context, alternatives, and rationale. This skill creates structured ADRs and supports consistent review, indexing, and lifecycle management.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "architecture-decision-records" from https://skillstore.io/skills/sickn33-architecture-decision-records.md and its manifest at https://skillstore.io/api/skills/sickn33-architecture-decision-records/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-architecture-decision-records.md Signed manifest GET /api/skills/sickn33-architecture-decision-records/manifest Signed lockfile GET /api/skills/sickn33-architecture-decision-records/lockfile

Test it

Using "architecture-decision-records". Document the decision to use PostgreSQL for an ecommerce platform that needs transactions, search, JSON attributes, and geospatial queries.

Expected outcome:

An accepted ADR compares PostgreSQL, MySQL, and MongoDB. It selects PostgreSQL, records tradeoffs, and lists implementation risks and mitigations.

Using "architecture-decision-records". Replace an earlier MongoDB decision after schemas stabilized and operating two databases became expensive.

Expected outcome:

A superseding ADR explains changed conditions, selects PostgreSQL, and defines phased dual-write, backfill, read migration, validation, and decommissioning work.

Using "architecture-decision-records". Propose event sourcing for order management, but identify unresolved design questions.

Expected outcome:

  • An RFC states auditability and temporal query goals.
  • It compares event sourcing with audit tables, change data capture, and a hybrid approach.
  • It records open questions about schema versioning, retention, and snapshots.

Security Audit

Safe
v6 • 7/23/2026 Open versioned report

All 32 static findings are false positives caused by Markdown fences, inline literals, documentation links, and a manual command example. No prompt injection, covert execution, credential access, or exfiltration intent was found in SKILL.md.

1
Files scanned
450
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (24)
SKILL.md:56-60 SKILL.md:60-66 SKILL.md:66-160 SKILL.md:160-161 SKILL.md:161-165 SKILL.md:165-190 SKILL.md:190-191 SKILL.md:191-195 SKILL.md:195-204 SKILL.md:204-208 SKILL.md:208-253 SKILL.md:253-257 SKILL.md:257-277 SKILL.md:277-283 SKILL.md:283-326 SKILL.md:326-332 SKILL.md:332-341 SKILL.md:341-345 SKILL.md:345-361 SKILL.md:361 SKILL.md:373-377 SKILL.md:377-395 SKILL.md:395-399 SKILL.md:399-421
🌐 Network access (8)
SKILL.md:158 SKILL.md:159 SKILL.md:324 SKILL.md:325 SKILL.md:441 SKILL.md:442 SKILL.md:443 SKILL.md:444
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-architecture-decision-records/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-architecture-decision-records/security.svg)](https://skillstore.io/skills/sickn33-architecture-decision-records?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-architecture-decision-records?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-architecture-decision-records/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-architecture-decision-records.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). architecture-decision-records security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-architecture-decision-records/audits/6

BibTeX citation

@techreport{sickn33-sickn33-architecture-decision-records-2026, author = {sickn33}, title = {architecture-decision-records security audit report (audit version 6)}, institution = {Skillstore}, year = {2026}, number = {6}, url = {https://skillstore.io/skills/sickn33-architecture-decision-records/audits/6}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "architecture-decision-records security audit report (audit version 6)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-architecture-decision-records/audits/6" identifiers: - type: other value: "skillstore:sickn33-architecture-decision-records:audit:6" description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Higher Skillstore usage
sickn33 Recommended Current

sickn33-architecture-decision-records

Skillstore Score 78
Evidence Confidence High
Skillstore usage 12
Updated

2026-09-09

wshobson

wshobson-architecture-decision-records

Skillstore Score 78
Evidence Confidence High
Skillstore usage 11
Updated

2026-09-09

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Record a Technology Choice

Compare database, framework, or platform options and capture the selected option with its rationale and consequences.

Review a Proposed Decision

Check whether an ADR covers viable alternatives, affected teams, security, cost, reversibility, and implementation follow-up.

Understand Historical Context

Use indexed and linked ADRs to learn why current systems exist and which earlier decisions were superseded.

Try These Prompts

Create a Basic ADR 
Create a lightweight ADR for [decision]. Include status, context, decision, positive consequences, negative consequences, and mitigations.
Compare Architecture Options 
Draft a standard ADR comparing [options] for [system]. Evaluate each option against [drivers] and explain the final recommendation.
Supersede an Existing ADR 
Write an ADR that supersedes [ADR identifier]. Explain changed conditions, migration phases, risks, mitigations, and links between both records.
Develop an RFC-Style Decision 
Create an RFC-style ADR for [proposal]. Cover motivation, detailed design, drawbacks, alternatives, unresolved questions, implementation plan, and review criteria.

Best Practices

  • Write the ADR before implementation and involve affected stakeholders during review.
  • State concrete decision drivers and present both benefits and costs for every viable option.
  • Preserve accepted records, then create linked ADRs when decisions change or become obsolete.

Avoid

  • Do not use ADRs for routine maintenance, minor patches, or isolated implementation details.
  • Do not omit context, rejected alternatives, negative consequences, or unresolved risks.
  • Do not silently edit accepted decisions or leave indexes and related records outdated.

Frequently Asked Questions

What is an Architecture Decision Record?
An ADR records the context, selected option, rationale, and consequences of a significant technical decision.
When should I create an ADR?
Create one for choices that affect architecture, security, integrations, platforms, data stores, or long-term engineering practices.
Which ADR format should I use?
Use a lightweight format for focused decisions and a standard or RFC format for complex, disputed, or cross-team decisions.
Should an accepted ADR be edited?
Preserve its historical content. Create a new linked ADR to deprecate or supersede the accepted decision.
Does this skill execute adr-tools commands?
No. It provides optional examples, but users must review and run commands in their own environment.
Can this skill decide the best architecture automatically?
No. It structures evidence and tradeoffs, but stakeholders must validate assumptions and approve the decision.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/architecture-decision-records

Ref

86d877f219e2131f05dd5b37c5e329c71c7b8ec4

Maintenance freshness

7/26/2026

Usage

8 downloads · 125 views

File structure

📄 SKILL.md

More from sickn33

View all

Related Skills

View all