pm-proto

Convert product requirements into a prototype design plan document.

46|8|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/konglong87/superPM --skill pm-proto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-proto
Source: https://github.com/konglong87/superPM/tree/main/skills/02-solution-design/pm-proto
Command: npx skills add https://github.com/konglong87/superPM --skill pm-proto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It helps product managers bridge the gap between PRD/MVP requirements and a concrete prototype plan by turning requirements into information architecture, page flows, and interaction-level specifications.

Core Features & Use Cases

  • Prototype scope selection: Guides you to choose overall, MVP-core, single-module, or optimization prototype scope so the output matches your stage.
  • Front-doc driven extraction: Pulls functional lists, interaction flows, user scenarios, page requirements, and journey touchpoints from PRD/MVP/journey inputs when available.
  • Prototype architecture to page flow: Produces an information architecture and designs key page flows plus interactive behavior for critical pages.
  • Structured deliverable output: Writes a prototype design document into docs/02-方案设计/原型设计方案.md.
  • Guardrails & exceptions: Includes fallback prompts when PRD is missing and a verification checklist to reduce incomplete/low-quality outputs.

Quick Start

Tell the assistant: “Use pm-proto to design the core MVP prototype, based on my existing PRD and MVP plan, and generate the prototype design document.”

Frequently Asked Questions about pm-proto

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

FAQPage Schema
How do I convert a PRD into an interactive prototype design plan?

To convert a PRD into an interactive prototype design plan, extract functional lists and user journey touchpoints to build information architecture and key page flows. This bridges requirement documents to page-level interaction design.

What is the best way to define information architecture from product requirements?

Defining information architecture from product requirements involves selecting a prototype scope like MVP-core or single-module, then pulling functional lists and user scenarios to structure page flows and interaction-level specifications.

Can I generate a prototype design document if my MVP plan is missing?

You can still generate a prototype design document if your MVP plan is missing because the workflow includes PRD-missing fallback handling prompts to guide extraction and reduce incomplete outputs.

How to map user journey touchpoints to page flows for a clickable prototype?

Mapping user journey touchpoints to page flows requires pulling journey inputs to design key page transitions and interactive behaviors for critical pages, outputting a structured prototype design document.

Does generating a prototype plan from requirements work for single-module optimization?

Generating a prototype plan from requirements works for single-module optimization by guiding you to choose overall, MVP-core, single-module, or optimization prototype scope so the output matches your current product lifecycle stage.

What limitations exist when extracting interaction flows from requirement documents?

A limitation when extracting interaction flows is the reliance on front-doc driven inputs; if PRD or journey context is missing, the output quality depends on fallback prompts and a verification checklist to catch incomplete specifications.