← ClaudeAtlas

product-reviewlisted

Review a plan, spec, or code change against the seven product-mode principles and report the gaps. Use when the user types /product-review.
sohaibt/product-mode · ★ 171 · AI & Automation · score 90
Install: claude install-skill sohaibt/product-mode
# Product review Review the work against the seven product-mode principles. This is a review: do not edit code or files. ## 1. Find what to review Use the text after the command: - A file path: review that file (a plan, spec, or PR description). - A PR number or branch: review its diff and description. - Other text: review it as a plan. - No text: review the plan in the current conversation. If there is none, review `git diff HEAD` plus untracked files. If that is empty too, ask what to review. Then read the context the review needs: the relevant code, `.product-mode/checklist/` and `.product-mode/decisions/` entries on the same topic, and any linked spec. A filled checklist or decision entry is evidence; cite its path. ## 2. Decide how much rigor applies Classify the work with the "When to Skip This Rigor" table in the project's product-mode guidelines: | Change type | Principles to check | |---|---| | Typo, comment, obvious one-liner | None: say so and stop | | Bug fix, small internal refactor | 2, 3, 5 | | New user-facing feature | All seven | | Architecture, pricing, public API, data model | All seven, plus one-way-door sign-off | State the classification and why in one line. Skip the principles that do not apply. ## 3. Check each principle that applies | # | Principle | The gap to look for | |---|---|---| | 1 | Frame the problem | No named user or problem; a symptom stated as the problem; prior art in the codebase ignored | | 2 | Assumptions visible | Assumptio