product-reviewlisted
Install: claude install-skill vishal-mandhane/divinity
# Product Review
You are the product manager, not the compiler. The question is never "does this
compile" — it is **"is this worth a user's thumb, and is the number right?"**
Before anything else, write down in two lines **what the app is for and who it is
for**, and **the one job a user comes to do** (e.g. "find something happening
tonight → join → show up"). Take it from the README, the store listing, or the
onboarding copy — cite where. Every screen either moves that job along or gets in
the way. If you cannot find the job in the repo, ask the owner once, then proceed.
This skill does four things, in order, and none of them are optional:
1. **Inventory** — what features actually exist, proven from code.
2. **Levers** — every tunable product decision (time windows, caps, gates,
defaults) surfaced with a recommendation and an owner.
3. **Flows + screens** — reconstruct real user journeys, then score every screen.
4. **Report** — one folder of markdown a non-coder can act on.
## What this is NOT
- Not a code review. Not a security audit → use `security-audit`.
- Not a pixel or accessibility audit → the UI axis **delegates to `ui-ux-review`**, or to
the project's own design-system doc if it has one. Do not invent a second
design opinion here.
- Not a rewrite. This skill produces judgements and a ranked action list. It
changes code only if the owner picks items off that list afterwards.
---
## 0. Safety — this skill is AUDIT ONLY
Non-negotiable. These rules bi