Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →notque/adr-consultation
Multi-agent consultation for architecture decisions.
Passed 8 of 15 test cases with the skill, and 3 of 15 without it.
and 13 more in the full report
10 fixed3 passed either way9 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are making a major core architecture change in adr/event-sourcing-core.md and requested a complex consultation. How many total reviewer agents should be dispatched?
| Checked | Without skill | With skill |
|---|---|---|
| Dispatches five reviewer agents for complex mode. | Missed | Passed |
| Includes reviewer-system in the dispatch list. | Missed | Passed |
The instructions your model reads when the skill loads.
Multi-agent architecture consultation that dispatches 3 specialized reviewers in parallel against an ADR and synthesizes their findings into a PROCEED or BLOCKED verdict. This is the gate between feature-lifecycle plan and implement phases for Medium+ decisions because challenging architecture decisions before implementation prevents costly post-implementation rework.
| Signal | Load These Files | Why |
|---|---|---|
| Phase 2 DISPATCH: consultation agent prompt templates | agent-prompts.md | Loads detailed guidance from agent-prompts.md. |
| orchestration corrections: dispatch, artifact, and verdict aggregation fixes | consultation-preferred-patterns.md | Loads detailed guidance from consultation-preferred-patterns.md. |
| core consultation patterns and Phase 3 artifact templates | consultation-patterns.md | Loads detailed guidance from consultation-patterns.md. |
| errors, error handling | error-handling.md | Loads detailed guidance from error-handling.md. |
Goal: Identify the ADR and prepare the consultation directory.
Step 1: Locate the ADR
Check for ADR path in this order:
adr/intent-based-routing.md).adr-session.json)Do not guess which ADR to consult on because an incorrect guess wastes a full consultation cycle. Reject absolute, traversing, or prose-derived paths. Register the exact repository-relative path through adr-query.py, compute its hash, then require the shared resolver/containment/registration check to pass:
python3 scripts/adr-query.py register --adr 'adr/{adr-name}.md'
python3 scripts/adr-query.py hash --adr 'adr/{adr-name}.md'
python3 scripts/adr-query.py validate-registration \
--repo-root . \
--adr 'adr/{adr-name}.md' \
--hash 'sha256:{digest}'
Keep that exact path and hash as consultation provenance. Stop if the resolver rejects the path, the content hash changes, or .adr-session.json names a different registration.
Even if this ADR was discussed informally, run the formal consultation because undocumented discussion produces no persistent artifacts and cannot be referenced by future sessions.
test cases passed, vs 3 / 15 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.