review-product
Critique a product, feature, or implementation against the relevant product, IA, UX, visual, accessibility, security, performance, reliability, and release expectations. Use before completion or when quality feels weak.
- License 许可
- MIT
- 最近更新
- 2026-09-27
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- review-product
- description
- Critique a product, feature, or implementation against the relevant product, IA, UX, visual, accessibility, security, performance, reliability, and release expectations. Use before completion or when quality feels weak.
03 SKILL.md 正文
Review Product
- Identify the review scope, documented user outcome, acceptance criteria, current stage, and applicable areas in
.docs/MANIFEST.md. - Select only the relevant review routes from
.docs/ROUTING.md; load project/feature truth before reusable guidance. - Research current category expectations when product quality, interaction patterns, visual conventions, or competitive completeness are part of the review.
- Inspect actual behavior, code, and rendered UI when available. Exercise realistic loading, empty, populated, error, long-content, responsive, permission, interruption, and recovery states that apply.
- Critique every applicable discipline: product usefulness/scope, journeys, IA, UX, interaction, visual/brand coherence, content, accessibility, frontend/backend architecture, data, security/privacy, performance, reliability, analytics/observability, testing, operations/support, and release readiness.
- Compare the implementation with project truth and evidence. Identify missing requirements, friction, inconsistencies, weak hierarchy, correctness risks, and operational gaps.
- Classify findings as blocking or improvement. Give every material finding a concrete remediation and identify the specification or decision that must change.
- Save durable findings under
.docs/validation/. Update project or feature truth when review reveals a requirements change. - Re-review remediated blocking findings before marking the work complete.
Completion means every applicable quality area has been intentionally resolved and no blocking finding remains.
04 同仓库更多 Skills
review-product
Critique a product or feature against applicable product, UX, technical, security, accessibility, and release expectations.
implement-feature
Implement or materially change a specified feature while preserving project truth and validating the result.
develop-product
Turn a vague software idea into a coherent product definition and initial project specification.
design-feature
Define or refine a product capability before implementation, including UX, IA, technical behavior, and acceptance criteria.
decide-architecture
Evaluate and record a consequential technical architecture decision using project constraints and routed guidance.
implement-feature
Implement or materially change a specified product capability while preserving project decisions, loading only relevant guidance, and keeping specifications synchronized with the code.