skills.rest
fengqiliu
fengqiliuCOMMUNITY
Explore all skills by this author →
GitHub

pm-beta-prototype-review

Evaluate interactive prototypes for usability and technical feasibility with P0–P3 severity classification.

2|Updated Mar 30, 2026
Search Tags:#feedback#prd#technical-feasibility#heuristic-evaluation#prototype-review#usability-evaluation#ux-checklist
One-click install
npx skills add https://github.com/fengqiliu/PM-Skills --skill pm-beta-prototype-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-beta-prototype-review
Source: https://github.com/fengqiliu/PM-Skills/tree/main/skills/pm-beta-prototype-review
Command: npx skills add https://github.com/fengqiliu/PM-Skills --skill pm-beta-prototype-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many prototype reviews are informal, inconsistent, and lack clear prioritization or technical validation, which leads to missed usability issues, rework, and unclear next steps. This Skill provides a repeatable process and output format so teams can efficiently evaluate interaction quality, identify severity-ranked problems, and confirm technical feasibility before development begins.

Core Features & Use Cases

  • Structured Checklist: A comprehensive interaction checklist covering basics, navigation, information presentation, user operations, edge cases, and flow completeness to ensure nothing is overlooked during review.
  • Usability Evaluation & Prioritization: Heuristic and cognitive-walkthrough approaches with a P0–P3 severity rubric and a template for recording issues, causes, and recommended fixes.
  • Technical Feasibility Assessment: A practical checklist and assessment table for front-end, back-end, third-party integrations, performance, and compliance constraints to surface implementation risks.
  • Feedback & Output Templates: Ready-to-use review report and meeting artifacts including summary judgment (pass/conditional/major revision), Q&A, pending confirmations, and follow-up schedule.
  • Use Cases: Design reviews, handoff to development, PRD validation, prototype QA sessions, and cross-functional alignment meetings.

Quick Start

Please review the provided prototype focusing on usability, classify found issues by P0–P3 severity, evaluate technical feasibility for front-end and backend constraints, and output a structured review report with must-fix items and suggested improvements.

Frequently Asked Questions about pm-beta-prototype-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a prototype review to include usability and technical feasibility?▼

Structure a prototype review by applying a heuristic evaluation checklist to assess usability, classifying issues by P0–P3 severity, and evaluating front-end, back-end, and third-party integration feasibility to output actionable feedback.

What is the best way to prioritize usability issues found during a design review?▼

Prioritize usability issues during a design review by using a P0–P3 severity rubric, which classifies problems by criticality and records the issue, cause, and recommended fix to ensure clear next steps.

How do I assess technical feasibility before handing off a prototype to developers?▼

Assess technical feasibility before developer handoff by applying a practical checklist that evaluates front-end, back-end, third-party integrations, performance, and compliance constraints to surface implementation risks.

Can I use a standard interaction checklist for both web and mobile prototype QA sessions?▼

Yes, you can use a standard interaction checklist for web and mobile prototype QA sessions, covering basics, navigation, information presentation, edge cases, and flow completeness to ensure comprehensive validation.

What should be included in a PRD validation report for cross-functional alignment?▼

A PRD validation report for cross-functional alignment should include a summary judgment of pass, conditional, or major revision, alongside must-fix items, Q&A, pending confirmations, and a follow-up schedule.

Why does my informal prototype review miss usability issues and technical constraints?▼

Informal prototype reviews miss usability issues and technical constraints because they lack a repeatable process, clear prioritization, and technical validation, leading to rework and unclear next steps.

Related Skills

Explore More Product & Management Skills→
yu13130122297yu13130122297

scout

Identify uncertainties in research framing, datasets, metrics, and baselines.

Community
Intermediate
akiotanaka847akiotanaka847
2

book-a-meeting

Propose three calendar time options and draft an outreach message for approval.

Community
Advanced
georgekhananaevgeorgekhananaev
27

uiux-toolkit

Evaluate UX quality across design systems with structured audit frameworks.

Community
Advanced
cjohnhansoncjohnhanson

design-review

Evaluate UI designs against Nielsen heuristics, Gestalt principles, and cognitive walkthrough.

Community
Advanced