specification-reviewlisted

Evidence boundary: Use when a fixed spec candidate needs a risk-triggered or explicitly requested read-only review. Own anchored findings and a PASS, CONCERNS, or FAIL verdict against current evidence and authorities; Skip when root self-review, editing, repair, or open-ended spec authoring is sufficient.
Dankosik/go-service-template-rest · ★ 6 · API & Backend · score 75

Install: claude install-skill Dankosik/go-service-template-rest

# Specification Review Must read [Specification Review](../../../docs/spec-first-workflow/phases/specification-review.md); it owns the evidence boundary, verdict consequences, and stop rule. Falsify the current fixed candidate read-only after reconstructing affected behavior from the accepted brief, research, runtime/generated contracts, and repository or consumer surfaces. Report only surviving anchored findings and the evidence boundary; do not emit per-lens receipts or pad a clean review. Missing policy ends with a named Specification Decision handoff; conformance Review starts separately after acceptance. Stop with `PASS`, `CONCERNS`, or `FAIL`; leave repair to the owning author.