spec-reviewlisted

Review a diff on the two axes a dev-flow project can check that a generic reviewer cannot: the **spec** it was built from (`.workflow/PRD.md` + `tasks.md`) and the **contract** it was built under (golden rules, `meta.json#stack`). Two parallel sub-agents, reported side by side and never merged, with a Fowler smell baseline as the floor. Use when the user says "review this branch", "spec review", "review since <ref>", "does this match the PRD?", "controlla il diff contro la spec", or dev-flow proposes it after a feature lands. Requires `.workflow/`; without one use the built-in `/code-review`. Records `meta.json#spec_review`; no phase bump. Not for: generic review with no spec (built-in `/code-review`), UI quality (`shadscan`), legal (`compliance-audit`), Vercel cost (`vercel-doctor`), or running tests (`write-tests`).
lukedj78/dev-flow · ★ 6 · Code & Development · score 78

Install: claude install-skill lukedj78/dev-flow

# spec-review — did we build what the PRD asked, the way the contract says? Two-axis review of the diff between `HEAD` and a fixed point: - **Spec** — does the change faithfully implement what `.workflow/PRD.md` / `tasks.md` asked for? - **Standards** — does it obey the contract this project was built under? Both run as **parallel sub-agents** so neither pollutes the other's context, then this skill reports them side by side. > **Credit.** The two-axis structure, the parallel-sub-agent split, the refusal to merge verdicts and > the Fowler smell baseline are adapted from Matt Pocock's `code-review` skill > ([mattpocock/skills](https://github.com/mattpocock/skills), MIT — the skill now lives at > [`docs/engineering/code-review.md`](https://github.com/mattpocock/skills/blob/main/docs/engineering/code-review.md); > both paths checked 2026-08-26) and > [the essay behind it](https://www.aihero.dev/skills-code-review). What's ours is the half his skill > has to search for: in a dev-flow project the spec and the standards are **at known paths**. ## Why this is not `/code-review` Claude Code ships a built-in `/code-review`, and Pocock's own write-up lists the name collision as a known problem. This skill is deliberately **not** that, in name or in remit: | | Built-in `/code-review` | `spec-review` | |---|---|---| | Reviews | the code, generically | the code **against this project's spec and contract** | | Knows | the diff | `.workflow/PRD.md`, `tasks.md`, `meta.json#stack`, `#a