Run any Skill in Manus with one click

$pwd:

adr-reviewer

Name: Adr Reviewer
Author: harumiWeb

// Review an ExStruct ADR draft for decision quality, overlap with existing ADRs and specs, evidence strength, rollout risk, and human-ownership escalations. Use only after adr-linter reports no unresolved high/medium findings on the current draft, and when you need design-review findings before merge or handoff.

Run Skill in Manus

$ git log --oneline --stat

stars:146

forks:22

updated:April 22, 2026 at 12:02

File Explorer

2 files

SKILL.md

readonly

name	adr-reviewer
description	Review an ExStruct ADR draft for decision quality, overlap with existing ADRs and specs, evidence strength, rollout risk, and human-ownership escalations. Use only after adr-linter reports no unresolved high/medium findings on the current draft, and when you need design-review findings before merge or handoff.

ADR Reviewer

Review the policy decision, not just the document shape.

Read

dev-docs/agents/adr-governance.md
dev-docs/agents/adr-criteria.md
dev-docs/agents/adr-workflow.md
dev-docs/specs/adr-review.md
The target ADR draft
Related ADRs, relevant public docs under docs/ when public API / CLI / MCP contracts are in scope, internal specs, tests, src paths, and issue / PR context
Existing adr-linter findings for the current draft

Workflow

Confirm the current draft has no unresolved adr-linter high / medium findings. Only proceed with design review after that precondition is met.
Read the ADR draft and identify the single policy question it is trying to resolve.
Check whether the draft overlaps with, contradicts, or should supersede an existing ADR or spec.
Verify that the cited Tests, Code, and Related specs actually support the claims being made, and include relevant public docs/ pages in scope when the ADR touches public API / CLI / MCP contracts.
Review whether compatibility, rollout, fallback, migration, or safety consequences are covered when relevant.
Detect human-owned decisions that AI should not settle, including public API break judgment, security or license calls, major directory reorganization, or unresolved product/spec direction.
Return one verdict:
- ready
- revise
- escalate

Output Contract

Return findings first, ordered by severity, and include:

verdict
scope
- draft
- related ADRs
- public docs
- specs
- src
- tests
- issue / PR context
findings

Each finding should include:

type
- decision-gap
- scope-conflict
- evidence-risk
- rollout-gap
- ownership-escalation
severity
summary
why it matters
suggested revision
evidence
- draft
- related sources

Also include top-level:

open questions
residual risks

Do not silently rewrite the ADR text. If the review hits a human-owned decision, return escalate instead of inventing a final policy.

related-skills.json

same repository

adr-linter.md

from "harumiWeb/exstruct"

Review an ExStruct ADR draft for required sections, status values, evidence quality, supersede links, and balanced consequences. Use when an ADR already exists in draft form and you need findings before review or merge.

2026-04-22146

exstruct-cli.md

from "harumiWeb/exstruct"

Use ExStruct CLI to validate, inspect, create, and edit Excel workbooks safely. Trigger when an agent needs `exstruct patch`, `exstruct make`, `exstruct validate`, `exstruct ops list`, or `exstruct ops describe`, especially for create-vs-edit decisions, dry-run workflows, backend constraints, or safe workbook-edit guidance.

2026-03-21146

adr-indexer.md

from "harumiWeb/exstruct"

Maintain ExStruct ADR index artifacts by scanning ADR files and synchronizing README, index.yaml, and decision-map.md metadata. Use when ADRs are added, updated, superseded, or reclassified and the repository needs a refreshed ADR map for humans and AI agents.

2026-03-13146

adr-reconciler.md

from "harumiWeb/exstruct"

Audit ExStruct ADRs against current specs, tests, and source code to detect policy drift, missing ADR updates, stale references, and evidence gaps. Use after merges, during periodic ADR audits, or when a review suspects that implementation and ADRs have diverged.

2026-03-13146

adr-drafter.md

from "harumiWeb/exstruct"

Draft a new ExStruct ADR or propose an update to an existing ADR from an issue, PR, diff, tests, and specs. Use when an ADR is required or recommended and you need a structured draft with context, decision, consequences, and evidence.

2026-03-13146

adr-suggester.md

from "harumiWeb/exstruct"

Determine whether a change in ExStruct needs an ADR, using repository-specific governance and criteria. Use when reading an issue, PR, review thread, or diff and you need a verdict of required, recommended, or not-needed, plus candidate ADR titles and related existing ADRs.

2026-03-13146

package.json

"author": "harumiWeb"

"repository": "harumiWeb/exstruct"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Computer Systems AnalystsComputer and Mathematical Occupations15-1211L4

Software Quality Assurance Analysts and TestersL4

name	adr-reviewer
description	Review an ExStruct ADR draft for decision quality, overlap with existing ADRs and specs, evidence strength, rollout risk, and human-ownership escalations. Use only after adr-linter reports no unresolved high/medium findings on the current draft, and when you need design-review findings before merge or handoff.

ADR Reviewer

Review the policy decision, not just the document shape.

Read

dev-docs/agents/adr-governance.md
dev-docs/agents/adr-criteria.md
dev-docs/agents/adr-workflow.md
dev-docs/specs/adr-review.md
The target ADR draft
Related ADRs, relevant public docs under docs/ when public API / CLI / MCP contracts are in scope, internal specs, tests, src paths, and issue / PR context
Existing adr-linter findings for the current draft

Workflow

Confirm the current draft has no unresolved adr-linter high / medium findings. Only proceed with design review after that precondition is met.
Read the ADR draft and identify the single policy question it is trying to resolve.
Check whether the draft overlaps with, contradicts, or should supersede an existing ADR or spec.
Verify that the cited Tests, Code, and Related specs actually support the claims being made, and include relevant public docs/ pages in scope when the ADR touches public API / CLI / MCP contracts.
Review whether compatibility, rollout, fallback, migration, or safety consequences are covered when relevant.
Detect human-owned decisions that AI should not settle, including public API break judgment, security or license calls, major directory reorganization, or unresolved product/spec direction.
Return one verdict:
- ready
- revise
- escalate

Output Contract

Return findings first, ordered by severity, and include:

verdict
scope
- draft
- related ADRs
- public docs
- specs
- src
- tests
- issue / PR context
findings

Each finding should include:

type
- decision-gap
- scope-conflict
- evidence-risk
- rollout-gap
- ownership-escalation
severity
summary
why it matters
suggested revision
evidence
- draft
- related sources

Also include top-level:

open questions
residual risks

Do not silently rewrite the ADR text. If the review hits a human-owned decision, return escalate instead of inventing a final policy.

adr-reviewer

ADR Reviewer

Read

Workflow

Output Contract

More from this repository

More from this repository

ADR Reviewer

Read

Workflow

Output Contract