tslateman/adr
skills/adr/SKILL.md
Generate Architecture Decision Records that capture the reasoning behind technical decisions. Use when the user asks to "create an ADR", "document a decision", "record why we chose X", or discusses architectural trade-offs worth preserving.
testing
Updated Apr 25, 2026
$ install --global
skillsauthnpx skillsauth add tslateman/duet 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 25, 2026, 6:25 PM16.5s1 file scanned
SKILL.md
- name:
- adr
- description:
- Generate Architecture Decision Records that capture the reasoning behind technical decisions. Use when the user asks to "create an ADR", "document a decision", "record why we chose X", or discusses architectural trade-offs worth preserving.
Architecture Decision Record Generator
Generate an Architecture Decision Record (ADR) based on the conversation context and any architectural decisions discussed.
ADR Format
Create a markdown file with this structure:
# ADR-[NUMBER]: [TITLE]
**Date:** [YYYY-MM-DD]
**Status:** [Proposed | Accepted | Deprecated | Superseded]
**Deciders:** [Who was involved]
## Context
What is the issue that we're seeing that is motivating this decision or change?
## Decision
What is the change that we're proposing and/or doing?
## Consequences
What becomes easier or more difficult to do because of this change?
### Positive
- [Benefit 1]
- [Benefit 2]
### Negative
- [Trade-off 1]
- [Trade-off 2]
### Risks
- [Risk and mitigation]
## Alternatives Considered
### [Alternative 1]
- **Description:** What was this option?
- **Rejected because:** Why didn't we choose it?
### [Alternative 2]
- **Description:** What was this option?
- **Rejected because:** Why didn't we choose it?
## References
- [Related PR, issue, or document]
- [Relevant discussion or prior art]
Instructions
-
Extract from context — Use the conversation to identify:
- The problem or decision being made
- Options that were discussed
- The chosen approach and rationale
- Trade-offs acknowledged
-
Find the ADR location — Look for existing ADRs:
docs/adr/ordocs/decisions/adr/at project root- If none exist, suggest creating
docs/adr/
-
Number appropriately — Check existing ADRs and use the next number
-
Write concisely — ADRs should be scannable:
- Context: 2-4 sentences
- Decision: 1-2 sentences
- Consequences: Bullet points
- Alternatives: Brief, focused on why rejected
-
Capture the why — The decision itself ages; the reasoning stays valuable
See Also
/research— Research informs the decision; ADR captures it/review— Reviews that surface architectural decisions belong in ADRsskills/FRAMEWORKS.md— Full framework index
Related Skills
tslateman/vibe-check
development
VerifiedTrustedCommunity
Judgment linter for vibe-coded output — reads the energy of the code, not just correctness. Use when the user says "vibe check", "check this vibe code", "does this hold up", "sanity check this AI code", or after a fast generation session before committing.
SKILL.mdUpdated Apr 25, 2026
tslateman/vamp
tools
VerifiedTrustedCommunity
Survey the project and choose what to play next
SKILL.mdUpdated Apr 25, 2026
tslateman/testing
development
VerifiedTrustedCommunity
Design test strategy using Beck's Test Desiderata — which properties matter, which tradeoffs to make. Use when the user asks "how should I test this", "what tests do I need", "review my test strategy", "is this well-tested", or when planning tests for a new feature or refactor.
SKILL.mdUpdated Apr 25, 2026
tslateman/sweep
testing
VerifiedTrustedCommunity
Post-op check for artifacts, damage, and stale references after agent work
SKILL.mdUpdated Apr 25, 2026