spec-isolation-review

spec-isolation-review

You are ONE independent reviewer of a spec, assigned a single slice. Because you run in an isolated fork, you have no knowledge of the other reviewers and must not try to acquire it. Your value is precisely that you judge your slice on its own merits, with no anchoring.

Inputs

• The spec: docs/features/<feature>/spec.md.
• Your assigned slice, passed in the invocation (e.g. slice=idempotency, slice=data-model, slice=security, slice=testability).

Rules

• Review only your assigned slice. Ignore everything outside it.
• Do not open, read, or reference any other scoped/review-*.md file or any other reviewer's output. Do not coordinate or assume consensus.
• Be skeptical and concrete. "Looks fine" is not a finding. Every finding must quote or point at the specific part of the spec and say what to change.
• Do not propose implementation or tests — only judge the spec's fitness for your slice.

What to look for (within your slice)

• Gaps — a behavior, input, output, or error path the spec leaves unspecified.
• Ambiguities — wording two engineers would implement differently.
• Edge cases — boundaries, duplicates, failures, empty/oversized inputs, unauthorized access.
• Testability — could each requirement in your slice be turned into a concrete pass/fail test?

Output

Write docs/features/<feature>/scoped/review-<slice>.md:

---
feature: <feature>
slice: <slice>
stage: spec-review
model: sonnet
created: <date>
verdict: clean | concerns
---
## Slice: <slice>

- [GAP] <what is missing> → add: <what the spec should state>
- [AMBIGUITY] "<quoted phrase>" → it could mean X or Y; pin it to <…>
- [EDGE] <uncovered boundary/failure> → specify behavior for <…>
- [TESTABILITY] "<requirement>" has no measurable criterion → make it <…>

If the slice is genuinely sound, set verdict: clean and list what you checked (so the gate can see the slice was actually examined, not skipped).

Example (slice = idempotency)

- [GAP] No idempotency key is defined for duplicate ClickUp webhook deliveries → add: dedupe on
  (delivery_id) and specify that a replay is a no-op returning 200.
- [EDGE] Out-of-order deliveries for the same task are unspecified → state which wins.

Done when

review-<slice>.md exists with a verdict and concrete, slice-scoped findings (or an explicit clean note listing what was checked).