Plugin

product-review-expert

product-review-expert is a Claude Code plugin for structured product and UX review. It is intended to help users analyze product requirement documents, workflow descriptions, page plans, and interaction designs before implementation or release. The plugin focuses on surfacing concrete quality issues rather than generating generic feedback. Its review scope includes workflow completeness, state-transition coverage, exception and edge-case handling, role and permission consistency, rule conflicts, action-path friction, missing feedback, and weak error-state design. The repository currently includes: 3 skills: product-audit logic-defect-review interaction-review 1 agent: senior-product-reviewer 1 local hook: a Stop hook that runs a bundled local script for lightweight normalization/logging purposes The plugin does not depend on external APIs, hosted services, MCP servers, OAuth flows, or user-provided secrets. It does not send user content over the network. The included hook only executes a local bundled script and writes a timestamped diagnostic log under ${CLAUDE_PLUGIN_DATA}. It does not modify user repository files or perform analytics collection. The plugin is documented with: a public GitHub repository a manifest in .claude-plugin/plugin.json installation and usage instructions in README.md semantic versioning and changelog license information Marketplace-facing usage is documented with namespaced commands such as: /product-review-expert:product-audit /product-review-expert:logic-defect-review /product-review-expert:interaction-review /product-review-expert:senior-product-reviewer The intended users are product managers, designers, business analysts, and teams reviewing process-heavy or stateful product designs such as approval systems, admin panels, internal tools, B2B workflows, and e-commerce flows.

• Published source
• Repository

Analysed

11 October 2026

Last observed

11 October 2026

What the code does

• Runs hooks automatically Hooks that execute without being called explicitly.

Having a capability is not wrongdoing; many tools need these to do their job. It tells you what to check before you install.

This is public metadata, not a safety certification or complete assessment. Static analysis cannot establish what a tool does at runtime.