← ClaudeAtlas

review-productlisted

Review a product from the user's perspective — build/refine a user persona, map their use cases (jobs-to-be-done), then audit the product for friction, gaps, and things to add or change. Triggers "review product", "product review", "review from the user's perspective", "product/UX critique", "what's missing for users". Use --live to also exercise the running app.
nielsmadan/skills · ★ 0 · Code & Development · score 75
Install: claude install-skill nielsmadan/skills
<!-- Generated from https://github.com/nielsmadan/agentic-coding — edits here are overwritten. --> # Review Product Review a product the way its users experience it, not the way its code is structured. Where `code-review` and the `review-*` family judge the implementation, this skill judges whether the *product serves the people using it*: it builds a profile of the user, maps the jobs they come to do, then walks those jobs through the product to find friction, gaps, and concrete things to add or change. Reusable findings (the persona and the use cases) are persisted to `docs/product/` and **refined** on each run, so the product's understanding of its users accumulates instead of being re-derived every time. The review itself is written to `docs/product/<date>-review.md` so it isn't lost. All of this lives under `docs/product/` as a section of the project's `docs/` tree, indexed by `docs/product/overview.md` once the section has several files (consistent with the `doc` skill's "index when warranted" convention). `docs/product/` is the **high-level, user-centric** layer (why, for whom, what's missing). It is the upstream of `docs/features/` (the "what it does" layer the `doc` skill owns and keeps in sync with the implementation; formerly `docs/prd/`). This skill owns `docs/product/` and does not write `docs/features/`; it only *checks* that the feature docs reflect the product understanding (Step 7). ## Usage ``` review-product # codebase + product descri