From docs-agent
Knowledge about Architecture Decision Records (ADRs) using MADR v4.0.0 format
npx claudepluginhub wsagency/ws-claude-marketplace --plugin docs-agentThis skill uses the workspace's default tool permissions.
This skill provides knowledge about creating and maintaining Architecture Decision Records using the MADR v4.0.0 (Markdown Any Decision Records) format.
Retrieves texts, DMs, one-time codes, and inspects threads in ECC workflows. Provides evidence of exact sources checked for verification before replies.
Delivers expertise for HS tariff classification, customs documentation, duty optimization, restricted party screening, and trade compliance across jurisdictions.
Process documents with Nutrient API: convert formats (PDF, DOCX, XLSX, images), OCR scans (100+ languages), extract text/tables, redact PII, sign, fill forms.
This skill provides knowledge about creating and maintaining Architecture Decision Records using the MADR v4.0.0 (Markdown Any Decision Records) format.
ADRs capture the "why" behind technical choices. They prevent teams from re-arguing settled decisions and give new team members context on past choices. ADRs are in ThoughtWorks' Technology Radar "Adopt" category and used by AWS and the UK Government Digital Service.
# [short title of solved problem and solution]
## Status
[Proposed | Accepted | Deprecated | Superseded by [ADR-XXXX](link)]
## Context and Problem Statement
[Describe the context and problem. Why is this decision needed?
What forces are at play? 2-3 sentences.]
## Decision Drivers
- [driver 1, e.g., technical constraint]
- [driver 2, e.g., business requirement]
- [driver 3, e.g., team expertise]
## Considered Options
1. [Option 1]
2. [Option 2]
3. [Option 3]
## Decision Outcome
Chosen option: "[Option N]", because [justification].
### Consequences
- Good, because [positive consequence]
- Good, because [another positive consequence]
- Bad, because [negative consequence or accepted tradeoff]
- Neutral, because [neither positive nor negative]
## Pros and Cons of the Options
### [Option 1]
- Good, because [argument]
- Good, because [argument]
- Neutral, because [argument]
- Bad, because [argument]
### [Option 2]
- Good, because [argument]
- Bad, because [argument]
### [Option 3]
- Good, because [argument]
- Bad, because [argument]
## More Information
[Links to relevant resources, related ADRs, or meeting notes]
Store ADRs in docs/decisions/ numbered sequentially:
docs/decisions/
├── 0001-use-graphql-over-rest.md
├── 0002-choose-tanstack-router.md
├── 0003-adopt-drizzle-orm.md
├── 0004-use-starlight-for-docs.md
└── README.md (index of all ADRs)
Add to your pull request template:
## Checklist
- [ ] Does this change require a new ADR? If yes, add one in `docs/decisions/`
references/ for detailed guidanceexamples/ for real-world ADR examples