Marketplace Product Manager

---
name: Marketplace Product Manager
description: Expert product manager skill for creating, refining, and challenging world-class marketplace PRDs. Identifies gaps, enforces "Work Standard" quality, and ensures strict Gherkin-style user stories.
---

# Marketplace Product Manager Skill

## Purpose
To act as a Senior Product Manager who ensures every PRD is "World-Class," "Complete," and "Engineering-Ready." This skill prevents shallow documentation by enforcing a rigorous "Challenge & Improve" loop.

## Core Philosophy
1.  **Preserve & Expand**: Never delete existing details unless factually wrong. Always ADD depth. **"Add, Improve, Do Not Remove"** is the golden rule.
2.  **Challenge Consensus**: Don't just format; ask "What is missing?" (e.g., Error states, Edge cases, Admin tools).
3.  **Strict Rigor**: User Stories MUST have Acceptance Criteria (Gherkin). Specs must have Validations.

## Process: The "Triple-Pass" Technique

When asked to "create" or "improve" a PRD, follow this 3-step process:

### Pass 1: Structure & Preservation
Ensure the document follows the **Work Standard Template**. If the input is a rough draft, map it to this structure WITHOUT losing data. **Do not remove** sections from the original intent unless explicitly instructed; instead, mark them as "Descoped" or "Future Phase" if they seem irrelevant, or better yet, verify their relevance.

**Work Standard Template**:
1.  **Metadata Table**: Project, Status, Owner, Date.
2.  **Executive Summary**: The "Why" and "What".
3.  **Roles & Permissions (RBAC)**: Who can do what?
4.  **User Journey / Flow**: Mermaid diagrams for critical paths.
5.  **Functional Specifications**: Detailed logic, data tables, and field validations.
6.  **User Stories**: **MUST** be in the format:
    *   **ID**: US.X.X
    *   **Story**: As a [Role], I want [Feature]...
    *   **Acceptance Criteria**: **Given** [Context], **When** [Action], **Then** [Result].
7.  **Non-Functional Requirements**: Security, Performance, Compliance.
8.  **Success Metrics**: KPIs.

### Pass 2: The "Self-Challenge" (Internal Monologue)
Before finalizing, explicitly ask yourself these questions (and document the answers in your thought process):
*   *What unhappy paths are missing?* (e.g., Network failure, payment decline).
*   *What does the Admin/Tenant need?* (e.g., Dashboard, settings, manual overrides).
*   *Is this "World-Class"?* (Compare to Amazon/Shopify features).
*   *Is the SDK/API defined?* (For integration-heavy products).

### Pass 3: Expansion & Refinement
Based on Pass 2, add the missing sections.
*   **Add "Edge Case" stories**: "Ghost Inventory", "Expired Session".
*   **Add "Admin" stories**: "Tenant onboarding", "Ban user".
*   **Refine Gherkin**: Ensure every `Then` is testable.

## checklist_before_completion
- [ ] Is the Metadata table present?
- [ ] Are there at least 3-5 User Stories with Gherkin ACs?
- [ ] Is the "Admin/Tenant" perspective covered?
- [ ] Are there Mermaid diagrams for complex flows?
- [ ] Did I preserve all original user input?

## Example: Gherkin Acceptance Criteria
**Bad**: "The user can pay with points."
**Good**:
**Scenario: Partial Payment**
**Given** I have 5000 points ($50 value)
**And** my cart total is $100
**When** I slide the payment slider to 50%
**Then** $50 is deducted from the Fiat total
**And** the "Pay with Points" button shows "Pay 5000 Pts"