majiayu000/spellbook / skills/prd-master
prd-master
VerifiedPRD writing and product definition expert. Use when writing PRDs, user stories, acceptance criteria, or prioritizing features. Covers RICE/MoSCoW frameworks, agile requirements, and specification best practices.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.2 KB |
| reference/acceptance-criteria.md | markdown | 20.4 KB |
| reference/extended.md | markdown | 6.7 KB |
| reference/prioritization.md | markdown | 24.6 KB |
| reference/user-stories.md | markdown | 18.1 KB |
| templates/prd-template.md | markdown | 22.8 KB |
templates/prd-template.md
View on GitHub# PRD: [Product/Feature Name]
**Status:** Draft | In Review | Approved
**Version:** 1.0
**Last Updated:** YYYY-MM-DD
**Author:** [Name]
**Stakeholders:** [Engineering Lead, Design Lead, etc.]
---
## Changelog
| Version | Date | Author | Changes |
|---------|------|--------|---------|
| 1.0 | YYYY-MM-DD | [Name] | Initial draft |
---
## Executive Summary
### Problem Statement
[In 2-3 sentences, describe the problem you're solving. What pain point are users experiencing? What opportunity are we missing?]
Example:
> Users abandon their carts 40% of the time because checkout requires account creation. Competitors offer guest checkout and have 25% lower cart abandonment. We're losing an estimated $2M in annual revenue due to this friction.
### Proposed Solution
[In 1-2 sentences, describe your solution at a high level]
Example:
> Enable guest checkout that allows users to complete purchases with just email, shipping address, and payment information—no account required. After purchase, optionally convert guest checkout to account with one-click.
### Success Metrics
[3-5 key metrics that define success]
Example:
- Reduce cart abandonment from 40% to 30% within 3 months
- Increase conversion rate by 15%
- 50% of guest checkout users convert to accounts within 30 days
- Maintain <2s checkout completion time (p95)
---
## Context & Background
### Why Now?
[What makes this the right time to build this?]
Example:
- Competitor analysis shows 8/10 top e-commerce sites offer guest checkout
- User research (n=150) showed account creation as #1 friction point
- Mobile traffic increased to 60% (mobile users resist creating accounts)
- Q4 holiday season approaching (high cart volume)
### Strategic Alignment
[How does this support company goals?]
Example:
- Aligns with 2025 goal: Increase revenue by 25%
- Supports "frictionless commerce" product vision
- Enables mobile-first strategy (mobile users prefer guest checkout)
### What Happens If We Don't Build This?
[Consequences of not shipping this feature]
Example:
- Continued revenue loss (~$500k/quarter)
- Competitive disadvantage vs. Amazon, Shopify competitors
- Negative user reviews citing checkout friction
- Mobile conversion gap continues to widen
---
## Goals & Success Metrics
### Business Goals
[Quantifiable business objectives]
Example:
- **Revenue:** Increase completed transactions by 10,000/month ($2M incremental revenue)
- **Conversion:** Improve checkout conversion from 60% to 75%
- **Customer Acquisition:** Reduce cost-per-acquisition by 20% (lower friction = higher conversion)
### User Goals
[What users will be able to accomplish]
Example:
- Complete purchase in under 2 minutes without creating account
- Save time on first purchase (no form duplication)
- Maintain privacy (optional account creation)
### Success Criteria
[How we'll measure success—include baseline, target, and timeline]
| Metric | Baseline | Target | Timeline |
|--------|----------|--------|----------|
| Cart abandonment rate | 40% | 30% | 3 months post-launch |
| Checkout completion time | 4 min | 2 min | Immediate |
| Guest checkout adoption | 0% | 60% of new users | 6 months |
| Guest→Account conversion | N/A | 50% | 30 days post-purchase |
| Mobile conversion rate | 45% | 65% | 3 months |
**Leading Indicators (track weekly):**
- Number of guest checkouts initiated
- Guest checkout completion rate
- Time to complete checkout
- Error rate during checkout
**Lagging Indicators (track monthly):**
- Overall revenue impact
- Customer lifetime value (CLV) comparison: guest vs account
- Support ticket volume related to checkout
---
## Target Users & Personas
### Primary Users
#### Persona 1: First-Time Mobile Shopper
**Demographics:**
- Age: 25-35
- Device: Mobile (70% iOS, 30% Android)
- Context: Shopping on-the-go, during commute
**Pain Points:**
- Doesn't want to create account for unknown brand
- Small mobile keyboard makes form-filling frustrating
- Skeptical of sharing personal info with new sites
- Needs fast checkout (limited time)
**Goals:**
- Complete purchase in <2 minutes
- Minimal form fields
- Trust that their data is secure
**Quote:**
> "I just want to buy this thing without creating another account I'll never use again."
#### Persona 2: Gift Purchaser
**Demographics:**
- Age: 30-50
- Device: Desktop or mobile
- Context: Buying gift for someone else
**Pain Points:**
- Doesn't want separate account for one-time gift
- Needs to ship to different address than billing
- Often in a hurry (last-minute gifts)
**Goals:**
- Quick checkout without commitment
- Easy gift note addition
- Ship to recipient address
**Quote:**
> "Why do I need an account? I'm just buying a birthday gift."
### Secondary Users
#### Persona 3: Privacy-Conscious Shopper
**Demographics:**
- Age: 25-45
- Device: Any
- Context: Values privacy and data minimization
**Pain Points:**
- Resents mandatory account creation
- Worried about data breaches and spam
- Wants minimal data sharing
**Goals:**
- Purchase without revealing unnecessary personal data
- Option to stay anonymous
- Control over marketing communications
---
## User Stories & Use Cases
### Epic: Guest Checkout
#### Must-Have Stories (MVP)
**Story 1: Guest Checkout Option**
```
As a first-time shopper,
I want to checkout without creating an account,
So that I can complete my purchase quickly.
Acceptance Criteria:
Given I have items in my cart and I'm not logged in
When I click "Checkout"
Then I see two options: "Continue as Guest" and "Login/Signup"
And the "Continue as Guest" option is visually prominent
Given I select "Continue as Guest"
When I proceed to checkout
Then I only need to provide: email, shipping address, payment info
And I don't see password or account creation fields
And I can complete checkout in <2 minutes
```
**Story 2: Guest Checkout Flow**
```
As a guest user,
I want a streamlined checkout experience,
So that I can purchase quickly without unnecessary steps.
Acceptance Criteria:
Given I'm checking out as guest
When I enter my email
Then the system validates email format
And checks if email exists (without revealing if account exists for security)
Given I've entered my shipping address
When I proceed to payment
Then my address is saved for this session only
And I can edit address before final confirmation
Given I've completed payment
When order is confirmed
Then I receive order confirmation email
And I can track order via email link (no login required)
```
**Story 3: Optional Account Conversion**
```
As a guest who completed checkout,
I want the option to create an account,
So that I can track my order and shop faster next time.
Acceptance Criteria:
Given I've completed guest checkout
When I land on order confirmation page
Then I see optional prompt: "Create account to track orders and save info"
And the prompt is non-intrusive (can be dismissed)
Given I click "Create Account"
When I enter just a password
Then an account is created with my guest checkout info
And I'm automatically logged in
And my order is associated with my new account
```
#### Should-Have Stories (Phase 2)
**Story 4: Guest Order Tracking**
```
As a guest purchaser,
I want to track my order without logging in,
So that I can know when my package arrives.
Acceptance Criteria:
Given I completed guest checkout
When I receive confirmation email with tracking link
Then I can click link to view order status
And I can see: order items, shipping status, estimated delivery
And I don't need to login or create account
```
**Story 5: Saved Guest Data**
```
As a repeat guest shopper,
I want my info pre-filled on return,
So that checkout is even faster next time.
Acceptance Criteria:
Given I've checked out as guest before (same device/browser)
When I return and add items to cart
Then my email and shipping address are pre-filled (if I opt-in to cookies)
And I can edit any pre-filled information
And I'm still not required to create account
```
---
## Requirements
### Functional Requirements
#### 1. Guest Checkout Flow
**FR-1.1:** System shall provide "Continue as Guest" option at checkout for non-logged-in users
**FR-1.2:** Guest checkout shall collect only essential information:
- Email address (required, validated)
- Shipping address (required, validated via address API)
- Payment information (required, processed via Stripe)
- Phone number (optional, for delivery updates)
**FR-1.3:** System shall validate all input fields with inline error messages
**FR-1.4:** Guest checkout shall complete in ≤3 steps:
1. Email + Shipping
2. Payment
3. Review + Confirm
**FR-1.5:** System shall send order confirmation email to guest users within 2 minutes
#### 2. Account Conversion
**FR-2.1:** System shall offer optional account creation after successful guest checkout
**FR-2.2:** Account conversion shall require only password (email + order info already captured)
**FR-2.3:** System shall associate guest order with newly created account
**FR-2.4:** System shall not spam or pressure users to create account
#### 3. Order Tracking
**FR-3.1:** System shall generate unique, secure order tracking link for guest orders
**FR-3.2:** Order tracking page shall not require authentication
**FR-3.3:** Tracking link shall expire after 90 days
#### 4. Data Handling
**FR-4.1:** Guest data shall be stored with same security standards as account users
**FR-4.2:** System shall comply with GDPR, CCPA for guest users (right to deletion, data export)
**FR-4.3:** Guest email addresses shall not be automatically added to marketing lists (requires opt-in)
### Non-Functional Requirements
#### Performance
**NFR-1.1:** Checkout completion time shall be <2 seconds per step (p95 latency)
**NFR-1.2:** System shall handle 10,000 concurrent guest checkouts
**NFR-1.3:** Payment processing shall complete within 5 seconds (p95)
#### Security
**NFR-2.1:** All guest data shall be encrypted at rest (AES-256)
**NFR-2.2:** All guest data transmission shall use TLS 1.3
**NFR-2.3:** Order tracking links shall use cryptographically secure tokens (256-bit)
**NFR-2.4:** System shall implement rate limiting: max 5 checkout attempts per IP per hour
**NFR-2.5:** Guest checkout shall comply with PCI DSS (payment handled by Stripe)
#### Accessibility
**NFR-3.1:** Guest checkout flow shall meet WCAG 2.2 AA standards
**NFR-3.2:** All form fields shall have proper labels and ARIA attributes
**NFR-3.3:** Checkout shall be fully keyboard navigable
**NFR-3.4:** Error messages shall be announced to screen readers
#### Usability
**NFR-4.1:** Guest checkout shall work on all modern browsers (Chrome, Safari, Firefox, Edge - latest 2 versions)
**NFR-4.2:** Guest checkout shall be responsive (mobile, tablet, desktop)
**NFR-4.3:** Form fields shall support autofill (address, payment)
**NFR-4.4:** Mobile keyboard types shall match input (email keyboard for email field, numeric for zip)
---
## Out of Scope
**Explicitly NOT included in this release:**
- ❌ Social login for guest users (deferred to Q3)
- ❌ Apple Pay / Google Pay integration (separate PRD)
- ❌ International shipping for guest checkout (US only for MVP)
- ❌ Guest wishlist or saved items (requires account)
- ❌ Guest returns/exchanges (requires account creation)
- ❌ Gift cards for guest checkout (Phase 2)
- ❌ Subscription products for guests (requires account)
**Rationale:**
Focus on core guest checkout flow first. Additional payment methods and features based on adoption data.
---
## Design & User Experience
### Design Files
[Link to Figma/Sketch files]
Example:
- [Guest Checkout Flow - Figma](https://figma.com/file/abc123)
- [Mobile Responsive Designs](https://figma.com/file/def456)
- [Error States & Validation](https://figma.com/file/ghi789)
### Key Design Decisions
**1. Checkout Option Presentation**
- Two equal-weight buttons: "Continue as Guest" | "Login"
- Guest option on left (Western reading order = priority)
- No dark patterns (e.g., "Skip" or diminutive language)
**2. Progress Indicator**
- Show 3-step progress: "Shipping" → "Payment" → "Review"
- Allows users to gauge time commitment
**3. Form Design**
- One column layout (reduces cognitive load)
- Labels above fields (better for mobile)
- Inline validation on blur
- Clear, actionable error messages
**4. Trust Signals**
- SSL lock icon visible
- "Secure Checkout" badge
- Payment logos (Visa, MC, Amex)
- Privacy policy link
### Accessibility Requirements
- ✅ WCAG 2.2 AA compliance
- ✅ Minimum touch target: 44x44px
- ✅ Color contrast ratio ≥4.5:1 for text
- ✅ Focus indicators visible (2px outline)
- ✅ Form labels properly associated with inputs
- ✅ Error messages linked via aria-describedby
- ✅ Screen reader tested (NVDA, VoiceOver)
### Mobile Considerations
- Simplified form (fewer fields on mobile)
- Autofill support for faster entry
- Sticky CTA button (always visible)
- Optimized keyboard types (email, number, tel)
- Large touch targets (min 44x44px)
---
## Technical Considerations
### Architecture Overview
```
┌─────────────┐
│ Frontend │
│ (React) │
└──────┬──────┘
│
│ REST API
▼
┌─────────────────┐
│ Backend API │
│ (Node.js) │
└────┬───────┬────┘
│ │
│ └──────► Stripe API (payment)
│
▼
┌────────────┐
│ PostgreSQL │
│ Database │
└────────────┘
```
### Data Model Changes
**New Table: `guest_orders`**
```sql
CREATE TABLE guest_orders (
id UUID PRIMARY KEY,
email VARCHAR(255) NOT NULL,
tracking_token VARCHAR(64) UNIQUE NOT NULL,
shipping_address JSONB NOT NULL,
order_total DECIMAL(10,2) NOT NULL,
stripe_payment_intent_id VARCHAR(255),
status VARCHAR(50) NOT NULL,
created_at TIMESTAMP NOT NULL,
expires_at TIMESTAMP NOT NULL,
converted_to_account_id UUID REFERENCES users(id),
INDEX idx_email (email),
INDEX idx_tracking_token (tracking_token),
INDEX idx_created_at (created_at)
);
```
**Modified Table: `orders`**
```sql
ALTER TABLE orders ADD COLUMN guest_order_id UUID REFERENCES guest_orders(id);
ALTER TABLE orders ADD COLUMN is_guest BOOLEAN DEFAULT FALSE;
```
### API Endpoints
**New Endpoints:**
```
POST /api/v1/checkout/guest
→ Initiate guest checkout
Body: { email, cart_id }
Response: { checkout_session_id, expires_at }
POST /api/v1/checkout/guest/:session_id/shipping
→ Submit shipping info
Body: { address, phone }
Response: { shipping_options, tax, total }
POST /api/v1/checkout/guest/:session_id/payment
→ Submit payment
Body: { stripe_payment_method_id }
Response: { order_id, tracking_token }
GET /api/v1/orders/track/:tracking_token
→ Track guest order (no auth)
Response: { order_details, shipping_status }
POST /api/v1/guest-orders/:id/convert
→ Convert guest order to account
Body: { password }
Response: { user_id, auth_token }
```
### Dependencies & Integrations
| Dependency | Purpose | Status |
|------------|---------|--------|
| Stripe API | Payment processing | Existing |
| Address Validation API (e.g., SmartyStreets) | Validate shipping addresses | New |
| Email Service (SendGrid) | Order confirmations | Existing |
| Analytics (Segment) | Track guest checkout funnel | Existing |
### Technical Risks & Mitigations
**Risk 1: Guest data security**
- **Mitigation:** Use same encryption, access controls as account users
- **Mitigation:** Regular security audits, penetration testing
- **Mitigation:** Implement rate limiting to prevent abuse
**Risk 2: Duplicate accounts (same email)**
- **Mitigation:** Check for existing email on account conversion
- **Mitigation:** Offer account merge flow if email exists
- **Mitigation:** Show warning: "An account with this email exists. Login instead?"
**Risk 3: Guest order fraud**
- **Mitigation:** Stripe fraud detection
- **Mitigation:** Velocity checks (max 3 orders per email per day)
- **Mitigation:** Require email verification for high-value orders (>$500)
**Risk 4: Session management complexity**
- **Mitigation:** Use Redis for session storage (fast, scalable)
- **Mitigation:** Clear expiration policy (30-minute session timeout)
- **Mitigation:** Comprehensive session cleanup job
---
## Rollout & Launch Plan
### Phased Rollout Strategy
**Phase 1: Internal Testing (Week 1-2)**
- Deploy to staging environment
- Internal team testing (QA, PM, Engineering)
- Fix critical bugs
**Phase 2: Beta (Week 3-4)**
- Release to 10% of US traffic (feature flag)
- Monitor key metrics daily
- Collect user feedback via Hotjar
- A/B test: Control (account required) vs Treatment (guest checkout)
**Phase 3: Gradual Rollout (Week 5-8)**
- Increase to 25% → 50% → 75% → 100%
- Monitor error rates, conversion rates
- Pause rollout if error rate >2% or conversion drops
**Phase 4: Full Launch (Week 9+)**
- 100% of traffic
- Announce feature (blog post, social media)
- Monitor support tickets
### Feature Flags
```javascript
// Feature flag configuration
{
"guest_checkout_enabled": {
"production": true,
"staging": true,
"development": true
},
"guest_checkout_rollout_percentage": {
"production": 100, // Start at 10, increase gradually
"staging": 100,
"development": 100
},
"guest_to_account_conversion": {
"production": true,
"staging": true,
"development": true
}
}
```
### Monitoring & Alerts
**Key Metrics to Monitor:**
| Metric | Alert Threshold | Action |
|--------|-----------------|--------|
| Guest checkout error rate | >2% | Investigate immediately |
| Guest checkout completion time | >5s (p95) | Performance investigation |
| Payment failure rate | >5% | Check Stripe integration |
| Email delivery failure | >1% | Check SendGrid status |
| Conversion rate drop | >10% vs baseline | Pause rollout, investigate |
**Dashboards:**
- Real-time guest checkout funnel (Grafana)
- Error logs (Sentry)
- Payment processing (Stripe dashboard)
- User behavior (Google Analytics, Mixpanel)
### Rollback Plan
**Trigger Conditions:**
- Error rate >5%
- Critical security vulnerability discovered
- Payment processing failure >10%
- Negative business impact (conversion drop >15%)
**Rollback Process:**
1. Set feature flag `guest_checkout_enabled` to `false`
2. Users automatically redirected to old checkout flow
3. In-flight guest checkouts allowed to complete
4. Incident post-mortem within 24 hours
5. Fix issues in staging before re-enabling
### Success Criteria for Full Launch
Before moving to 100% rollout:
- ✅ Error rate <1%
- ✅ Guest checkout completion rate >70%
- ✅ Overall conversion rate improved by ≥10%
- ✅ No critical bugs in backlog
- ✅ Support team trained on guest checkout
- ✅ Documentation published
---
## Open Questions & Risks
### Open Questions
**Q1: Should we allow guest checkout for high-value orders (>$1000)?**
- **Status:** ⏳ Pending decision from Finance team
- **Options:**
a) No limit (trust Stripe fraud detection)
b) Require email verification for orders >$500
c) Require phone verification for orders >$1000
- **Decision deadline:** 2 weeks before launch
- **Owner:** Finance Lead + PM
**Q2: How long should we retain guest order data?**
- **Status:** ⏳ Pending Legal review
- **Options:**
a) 90 days (for returns/support)
b) 1 year (for analytics)
c) Indefinitely (until user requests deletion)
- **Decision deadline:** Before beta launch
- **Owner:** Legal + Data Privacy team
**Q3: Should guest users receive marketing emails?**
- **Status:** 🟢 Resolved - No, unless explicit opt-in
- **Decision:** Respect anti-spam laws, require double opt-in for marketing
- **Owner:** Marketing Lead
### Risks
| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
| Guest checkout cannibalizes account creation | High | Medium | Offer compelling post-purchase conversion incentive (discount, points) |
| Increased fraud due to lower barriers | Medium | High | Leverage Stripe Radar, implement velocity checks, email verification |
| Support burden increases (password resets, order lookups) | Medium | Low | Clear order tracking via email, comprehensive FAQs |
| Technical complexity delays launch | Low | Medium | Early technical spike, dedicated engineering resources |
| Privacy compliance issues (GDPR, CCPA) | Low | High | Legal review before launch, privacy policy updates |
---
## Stakeholder Sign-Off
| Stakeholder | Role | Status | Date | Comments |
|-------------|------|--------|------|----------|
| Jane Doe | Product Lead | ✅ Approved | 2025-03-15 | Prioritize for Q2 launch |
| John Smith | Engineering Lead | ✅ Approved | 2025-03-16 | Feasible, 6-week estimate |
| Sarah Johnson | Design Lead | ✅ Approved | 2025-03-15 | Designs ready |
| Mike Chen | Legal | ⏳ Pending | | Reviewing data retention policy |
| Lisa Wang | Finance | ✅ Approved | 2025-03-17 | Approved with fraud monitoring |
---
## Appendix
### Competitive Analysis
| Competitor | Has Guest Checkout? | Notable Features |
|------------|---------------------|------------------|
| Amazon | Yes | One-click for guests if cookies enabled |
| Shopify stores | Yes | Standard feature across all stores |
| Target | Yes | Order tracking via email only |
| Walmart | Yes | Option to save info for next time |
| Best Buy | Yes | Guest checkout + easy account creation |
**Insight:** All major competitors offer guest checkout. It's table stakes, not a differentiator.
### User Research Summary
**Method:** User interviews (n=50) + Survey (n=500)
**Key Findings:**
- 68% prefer guest checkout for first purchase with unknown brand
- 42% eventually create account if first experience is positive
- Account creation is #1 cited reason for cart abandonment (38%)
- Mobile users especially resistant to account creation (72%)
**Quotes:**
> "I hate creating accounts. I use guest checkout whenever possible."
> — Sarah, 29, frequent online shopper
> "If I like the product and service, I'll create an account later. Don't force me upfront."
> — Mike, 35, occasional buyer
### Analytics Data
**Cart Abandonment Analysis (Last 90 Days):**
- Total carts created: 250,000
- Carts that reached checkout: 150,000 (60%)
- Abandoned at checkout: 60,000 (40%)
- Reason (exit survey): 65% cited "Don't want to create account"
**Estimated Revenue Impact:**
- Abandoned cart value: $6M
- If 50% of those complete as guest: +$3M revenue
- Conservative estimate (30% conversion): +$1.8M revenue
### Related Documents
- [Checkout Redesign - Figma](https://figma.com/file/abc123)
- [User Research Report - Guest Checkout](https://docs.google.com/document/abc)
- [Technical Spec - Backend Implementation](https://github.com/company/docs/guest-checkout-spec)
- [Security Review - Guest Data Handling](https://confluence.company.com/security-review-001)
---
## Document History
This PRD is a living document. Update version number and changelog for significant changes.
**Review Schedule:**
- Weekly during development
- Monthly post-launch (first 3 months)
- Quarterly thereafter
**Feedback:**
Contact [Product Manager Name] at pm@company.com
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |