the-own-lab/adr
skills/adr/SKILL.md
Write Architecture Decision Records for significant technical decisions. Use when a decision will affect future development.
development
Updated Apr 21, 2026
$ install --global
skillsauthnpx skillsauth add the-own-lab/Claude-company-of-one adrInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 10:05 PM25.6s1 file scanned
SKILL.md
- name:
- adr
- description:
- Write Architecture Decision Records for significant technical decisions. Use when a decision will affect future development.
Architecture Decision Records
Document significant technical decisions so future developers (and future pipeline runs) understand the reasoning.
When to Write an ADR
- Choosing a technology, framework, or library
- Changing an architectural pattern (e.g., monolith to services, REST to GraphQL)
- Adding a significant dependency
- Changing the security model or authentication approach
- Any decision that constrains or enables future development directions
ADR Format
Header
# ADR-{NNN}: Title of Decision
Status: Proposed | Accepted | Deprecated | Superseded by ADR-{NNN}
Date: YYYY-MM-DD
Context
What is the situation that motivates this decision? Describe the forces at play:
- Technical constraints
- Business requirements
- Team capabilities
- Timeline pressure
Decision
State the decision clearly and concisely. Use active voice: "We will use X for Y because Z."
Consequences
Positive
- Benefits gained from this decision
Negative
- Trade-offs accepted
Risks
- What could go wrong and under what conditions
Alternatives Considered
| Alternative | Pros | Cons | Reason Not Chosen | | ----------- | ---- | ---- | ----------------- | | Option A | ... | ... | ... | | Option B | ... | ... | ... |
Template
Read the template before producing the ADR (includes Mermaid diagrams):
Read ${CLAUDE_PLUGIN_ROOT}/templates/ADR.md
Numbering
ADRs are numbered sequentially: ADR-001, ADR-002, etc. Numbers are never reused. If a decision is superseded, the original ADR is updated with a status change pointing to the new ADR.
Storage
ADRs are the ONLY pipeline artifact that goes into the project repo. Store them in docs/adr/ — this is git-tracked because architectural decisions have lasting impact on future development.
Lifecycle
- Proposed — Draft written, open for discussion
- Accepted — Decision agreed upon and in effect
- Deprecated — Decision no longer relevant (context changed)
- Superseded — Replaced by a newer ADR (link to successor)
Related Skills
the-own-lab/write-brief
documentation
VerifiedTrustedCommunity
Update BRIEF.md sections during a command run. Any skill that produces a brief-persisted artifact calls this to write it back.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/verify
development
VerifiedTrustedCommunity
Post-code check: run tests + confirm TODO acceptance items map to passing tests; applies a security lens but is not a separate scan.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/update-docs
documentation
VerifiedTrustedCommunity
Command post-step: write CHANGELOG + TODO once per command run. One call, not per-skill doc writes.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/spec-writing
content-media
VerifiedTrustedCommunity
Author REQUIREMENTS.md + DESIGN.md + TODO.md for a feature. The three files are one contract; they ship together.
SKILL.mdUpdated Apr 22, 2026