---
id: "action-pm-prototype-handoff"
type: "action-item"
source_timestamps: ["00:15:15"]
tags: ["product-management", "agile-workflow"]
related: ["framework-new-pm-workflow", "claim-pm-workflow-shift"]
action: "Require PMs to generate interactive code prototypes via Claude Design instead of writing text-heavy PRDs."
outcome: "Reduces ambiguity in engineering handoffs and accelerates the development cycle by providing a functional source of truth."
speakers: ["Nate B. Jones"]
sources: ["s05-claude-design-30min"]
sourceVaultSlug: "s05-claude-design-30min"
originDay: 5
---
# Shift PMs to Prototype Handoffs (Not PRDs)

## Action
Require PMs to generate **interactive code prototypes** via [[entity-product-claude-design-d5]] instead of writing text-heavy PRDs.

## How (the operational steps)
Follow [[framework-new-pm-workflow]]:
1. Paste acceptance criteria into Claude Design.
2. Prompt it for the user flow.
3. Ensure all states are built (empty, loading, error, success).
4. Attach the resulting interactive prototype directly to the Jira ticket.

## Outcome
- **Reduced ambiguity** in engineering handoffs.
- **Faster development cycles** because the spec is the running prototype.
- Engineering review focus shifts from spec interpretation to scale, architecture, and edge cases — see [[claim-engineering-focus-shift]].

## Caveat
From enrichment: this is supported anecdotally in early-adopter teams; not yet validated at scale. Engineering still needs to review for production edge cases.