pm-prototype-flow

Frame a problem into a prototype flow brief with entry point, main flow, risky states, and fallback path.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/chenluhan/skill --skill pm-prototype-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-prototype-flow
Source: https://github.com/chenluhan/skill/tree/main/.agents/skills/pm-prototype-flow
Command: npx skills add https://github.com/chenluhan/skill --skill pm-prototype-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts vague problem framing into a clear, handoff-ready product flow and prototype brief, enabling faster alignment before heavy specification.

Core Features & Use Cases

  • Prototype brief: creates entry point, main flow, screen/state list, and at least two risky states with a fallback path.
  • Interaction sketch: describes user actions and system responses to communicate flow.
  • Handoff-ready outputs: provides a structured brief ready for state-matrix and delta-spec handoff.

Quick Start

Describe a user problem framing and generate a prototype flow with entry point, main flow, screens, two risky states, and a fallback path.

Frequently Asked Questions about pm-prototype-flow

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

FAQPage Schema
How do I convert problem framing into a handoff-ready prototype flow?

To convert problem framing into a prototype flow, describe the user problem to generate a structured brief. This creates an entry point, main flow, screen list, risky states, and fallback path for handoff.

What is a prototype brief and when do I need it for product definition?

A prototype brief is a structured document specifying an entry point, main flow, screen list, and fallback path. You need it during early-stage product definition to achieve alignment before writing heavy specifications.

How do I structure an interaction sketch with risky states and a fallback path?

Structure an interaction sketch by defining user actions and system responses across a screen sequence. Include at least two risky states and a fallback path to ensure robust flow communication for product teams.

Can I use this for early-stage product definition without dependencies?

Yes, you can use this for early-stage product definition without dependencies. It operates independently to frame problems and generate prototype planning artifacts for design and product groups.

What is the best way to prepare handoff targets for state-matrix and delta-spec?

The best way to prepare handoff targets is to generate a structured prototype brief detailing entry points, screen sequences, and risky states. This output explicitly feeds into downstream state-matrix and delta-spec processes.