---
id: "framework-new-pm-workflow"
type: "framework"
source_timestamps: ["00:15:15", "00:15:56"]
tags: ["product-management", "agile"]
related: ["claim-pm-workflow-shift", "action-pm-prototype-handoff", "framework-anthropic-creation-loop"]
steps: ["Paste user stories and acceptance criteria into Claude Design.", "Prompt the AI to generate a user flow that satisfies the criteria.", "\"Instruct the AI to generate all necessary UI states (empty", "loading", "error", "success).\"", "\"Attach the generated", "interactive code prototype directly to the engineering Jira ticket.\""]
sources: ["s05-claude-design-30min"]
sourceVaultSlug: "s05-claude-design-30min"
originDay: 5
---
# The Prototype-Driven PM Workflow

## Purpose
A new operational framework for Product Managers that replaces the traditional Product Requirements Document (PRD). See [[claim-pm-workflow-shift]].

## The Four Steps
1. **Paste** the user stories and acceptance criteria into [[entity-product-claude-design-d5]].
2. **Prompt** the AI to generate a user flow satisfying those criteria.
3. **Instruct** the AI to build out all necessary UI states — empty, loading, error, success — not just the happy path.
4. **Attach** the generated, interactive code prototype directly to the engineering Jira ticket as the source of truth.

## Why It Beats the PRD
- The prototype is **unambiguous** — engineers see exactly what to build, including edge states.
- Time-to-handoff drops because there is no designer translation step.
- Engineering review focuses on production concerns, not specification archaeology — see [[claim-engineering-focus-shift]].

## Operationalization
The action item [[action-pm-prototype-handoff]] is the deliberate adoption of this framework as team policy. This is a specific instantiation of the more general [[framework-anthropic-creation-loop]].