PRD — E-commerce Product Manager

Overview

Draft and validate PRDs for e-commerce: catalog, cart/checkout, payments, inventory, merchandising, conversion.

Example Conversation

You: I need a PRD for our new checkout and payment flow. We have catalog and cart; we’re adding a new payment provider and one-click checkout.

Agent: I’ll use the E-commerce PRD skill: load best-practices and sections checklist, draft from the template (Catalog & merchandising, Cart & checkout, Payments), then run validate_prd_structure.

Agent: Created prd-checkout-payments.md. Validation: NEEDS_REVISION — one placeholder in Payments. Fixed. Re-run: PASS.

What the Tools Validate

validate_prd_structure checks the PRD for:

Required sections — Overview, Goals, User personas, Catalog & merchandising, Cart & checkout, Payments, Success metrics, Non-functional requirements. Missing sections are reported as errors.
Placeholders — Flags [TODO], [TBD], or bracketed placeholders so you can replace them before finalising.

Output: PASS when there are no errors and no unfilled placeholders; NEEDS_REVISION when only warnings; FAIL when required sections are missing.

Output Excerpt

E-commerce PRD (excerpt):

## Cart & checkout

- **Cart:** Persisted for guest and logged-in; 30-day expiry for guest
- **Checkout steps:** Shipping → Payment → Review. One-click for returning customers.
- **Edge cases:** Out-of-stock item removal; tax by region

## Payments

- **Methods:** Cards (Stripe), PayPal, BNPL (provider TBD)
- **Security:** PCI-DSS via Stripe; no card data stored
- **Refunds:** Via Stripe dashboard; sync to order history

Getting Started

Add your context (catalog, cart, payment providers) to the project workspace, then activate the PRD — E-commerce Product Manager skill. The agent will guide you through drafting and validating with validate_prd_structure.