adr-consultation

Coordinate parallel reviewers to assess ADRs and enforce blocking gates.

415|44|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/notque/vexjoy-agent --skill adr-consultation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adr-consultation
Source: https://github.com/notque/vexjoy-agent/tree/main/skills/process/adr-consultation
Command: npx skills add https://github.com/notque/vexjoy-agent --skill adr-consultation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents architecture decisions from moving forward without challenging assumptions, assessing user impact, and checking system-level risks before implementation.

Core Features & Use Cases

  • Multi-agent ADR consultation: Dispatches three specialized reviewers (contrarian, user-advocate, and meta-process) to evaluate an ADR and produce lens-specific verdicts.
  • File-based, reproducible synthesis: Writes each reviewer’s output to disk and then synthesizes a unified PROCEED or BLOCKED verdict from the persisted artifacts.
  • Hard gate on blocking concerns: Enforces that any severity: blocking issue results in a BLOCKED verdict, preventing rationalization-driven “skip” behavior.
  • Use Case: Before implementing a Medium+ architecture change (e.g., new subsystem or major decision), consult on the ADR to reduce costly post-implementation rework.

Quick Start

Run the adr-consultation Skill with your intent like “consult on ADR <name or path> before implementing this architecture change.”

Frequently Asked Questions about adr-consultation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review an Architecture Decision Record before implementation?▼

To review an Architecture Decision Record before implementation, dispatch parallel multi-agent consultations that evaluate premises, user impact, and system health, synthesizing concerns into a unified PROCEED or BLOCKED verdict.

What is multi-agent consultation for architecture decisions?▼

Multi-agent consultation for architecture decisions dispatches specialized reviewers to evaluate an ADR from contrarian, user-advocate, and meta-process perspectives, producing lens-specific verdicts synthesized into a final decision.

Can I enforce a hard gate on blocking concerns during architecture review?▼

Yes, you can enforce a hard gate on blocking concerns during architecture review. Any severity blocking issue automatically results in a BLOCKED verdict, preventing rationalization-driven skip behavior.

How do I synthesize architecture review feedback into a reproducible format?▼

Synthesize architecture review feedback into a reproducible format by writing each reviewer's output to disk as artifacts, then consolidating concerns into concerns.md and synthesis.md files for a unified verdict.

When do I need to consult on an Architecture Decision Record?▼

You need to consult on an Architecture Decision Record before implementing Medium or larger architecture changes, such as adding a new subsystem, to challenge assumptions and reduce costly post-implementation rework.

Does architecture decision gating work without external dependencies?▼

Architecture decision gating works without external dependencies, using dispatched Task calls to write reviewer artifacts to disk and synthesize concerns internally for a final PROCEED or BLOCKED verdict.