matthew-a-carr/review-spec
Cross-artefact consistency and quality review of an approved or draft SPEC. Use when the user says "review SPEC-NNN," before `implement-spec` runs, or by `draft-spec` / `revise-spec` before opening or updating a spec PR. Checks the SPEC against the constitution, ADRs, parent epic (if any), and tech debt register. Read-only — produces a structured report, never edits files.
78
90%
Does it follow best practices?
Impact
80%
1.42xAverage score across 1 eval scenario
Passed
No known issues
task.mdevals/scenario-1/
Review a User Role Management Specification
Problem/Feature Description
The security team has drafted SPEC-018, covering a new role management system that will let organization administrators assign and revoke user roles. The spec is being reviewed before it enters the implementation queue.
The project documentation is in the inputs/ directory. The spec to review is at inputs/docs/specs/SPEC-018-user-role-management.md. The project constitution is at inputs/CONSTITUTION.md, ADR index at inputs/docs/decisions/README.md, and the tech debt register at inputs/docs/tech-debt.md.
Produce a structured review report covering all six review passes. The team wants to know if this spec is ready to hand to developers, or if it needs further revision.
Output Specification
Write your review to review-report.md in your working directory. Do not modify any files in the inputs/ directory. Do not start implementing the SPEC — only review it and report.