---
name: review-current-slice
description: Review the current slice against the active task, definition of done, and UX scorecard, then write a strict pass/fail review file.
disable-model-invocation: true
allowed-tools: Read, Write, Edit, Glob, Grep, Bash
---

Use this skill before declaring a slice done.

## Steps
1. Read:
   - `docs/planning/active-task.md`
   - `docs/quality/definition-of-done.md`
   - `docs/quality/ux-scorecard.md`
   - `docs/reviews/latest-review.md` if it exists
2. Review the current implementation against the task.
3. If UI was touched, score each UX category.
4. Write the result to `docs/reviews/latest-review.md`.

## Output requirements
The review file must include:
- reviewed surface
- verdict: PASS or FAIL
- overall score
- category scores when UI was touched
- what was verified
- main weaknesses
- required rework

## Rules
- overall UX must be >= 9.0
- no UX category may be below 8.5
- if the bar is not met, the verdict is FAIL