Validate adr
Skill exchanet/method_enterprise_builder_planning/agents/antigravity/.agent/skills/validate-adr
ποΈ Universal 8-phase methodology for planning and building enterprise-grade, mission-critical software with AI coding agents. Supports Cursor AI, Claude Code, Kimi Code, Windsurf & Google Antigravity. Includes ADR validator, microtask linter & CI/CD templates. β₯99% test coverage. MIT.
npx -y skills add exchanet/method_enterprise_builder_planning --skill validate-adrAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 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
Validate Architecture Decision Records against 11 enterprise rules before marking as Accepted
SKILL.md
2.4 KB, as published. Nobody here has run it
Skill: Validate ADR
Purpose
Run the enterprise ADR Validator against one or more ADR files to check compliance with 11 validation rules.
When to use
- After generating any ADR in Phase 5
- Before marking an ADR as Accepted
- When the user explicitly requests ADR validation
- As part of the Phase 5 gate check
How to run
# Single ADR
node packs/enterprise-architecture-pack/validators/adr-validator/src/index.ts \
--format=console docs/adr/ADR-001-isolation.md
# All ADRs in directory
node packs/enterprise-architecture-pack/validators/adr-validator/src/index.ts \
--strict docs/adr/
Rules checked
| Rule ID | Severity | Check |
|---|---|---|
| ADR-STR-001 | error | Required sections (Context, Decision) present |
| ADR-STR-002 | error | ADR has a title |
| ADR-STR-003 | warning | Context section is not empty (β₯50 chars) |
| ADR-ENT-001 | error | β₯2 alternatives documented |
| ADR-ENT-002 | error | Alternatives include rejection reasons |
| ADR-ENT-003 | error | Compliance Impact section present |
| ADR-ENT-004 | error | Valid status (Proposed/Accepted/Deprecated/Superseded) |
| ADR-ENT-005 | error | ISO 8601 date format (YYYY-MM-DD) |
| ADR-COMP-001 | warning | Security ADRs reference a compliance standard |
| ADR-COMP-002 | warning | Consequences section present |
| ADR-COMP-003 | warning | Regulated ADRs name their deciders |
Output interpretation
Console format:
β docs/adr/ADR-001-isolation.md β PASS
β docs/adr/ADR-002-saga.md β FAIL
β [ADR-ENT-001] Enterprise ADRs must document at least 2 alternatives.
β Add a table with at least 2 alternative approaches...
Gate rule: An ADR with any error-severity violation cannot be marked as Accepted.
Fix all errors, re-run the validator, confirm ALL PASSED, then mark the ADR as Accepted.
Integration with Phase 5
After generating an ADR:
- Save the file:
docs/adr/ADR-NNN-title.md - Load
@skill validate-adr - Run the validator (terminal command or code execution)
- If FAIL: fix violations, re-run validator
- If PASS: mark ADR as Accepted, proceed to next decision