reviewing-feature-spec — SKILL.md

Variant: standard · When to use: judging a finished feature spec as an acceptance gate — checking it is implementable and testable, then emitting VERDICT: approve|revise with actionable findings. Greenfield, or an amend (delta-scoped).

Overview

This skill is the review half of a producing/judging feature-spec pair. Loaded by a reviewer who holds a finished feature specification — the document below the PRD that says how each feature behaves — it judges that spec against one question: can an engineer build it and a tester verify it without asking the author, so planning can cut tasks from it? It applies a fixed 10-condition implementability + testability checklist (the same bar a feature-spec author produces to, so the produce-bar and the review-bar do not drift), then emits a single machine-parseable verdict plus findings the author can act on in one revision pass. It is an acceptance gate — it does not author, fix, or rewrite the spec; it judges and returns findings, and the producer revises.

The bar is single-sourced with the author. The author's techniques — EARS phrasing, decision tables, use-case flow precision, archetype overlays, the 29148 vocabulary — are aids the reviewer judges by OUTCOME (is the behavior unambiguous? is the rule-set complete? are the AC testable for this feature's nature?), never conditions to demand. Minting a condition the author doesn't produce to (e.g. "must use EARS", "must have a UI section") is the cardinal drift this skill guards against.

When to activate

• A finished feature spec needs an accept/revise decision before engineering plans or builds from it.
• You are the independent reviewer / gate for a feature spec a producer just authored.
• Re-judging a revised feature spec after a prior revise verdict.
• Reviewing an amend — an approved spec + a change request — as a delta-scoped review (cond-10).

Do NOT activate when: