Board Save to Closet Jina Park · Persona

Board

Sprint 6 · Closet · Apr 12 – Apr 26 · Day 3 of 14
Backlog5
User research synthesis — Q2 closet behavior interviews.
M
Product
Empty-state illustration for first-time closet visitors.
K
Design
Influencer outreach list — 50 fashion creators, tier A/B/C.
S
Growth
Affiliate partner intros — Net-a-Porter, Ssense, MR PORTER.
S
Growth
Migration: add closet_items table + indexes.
A
db
To Do3
Decision
Onboarding tone — playful or warm-professional?
M
Needs Lisa's call
MilestoneApr 26
Closet beta launch to first 50 users.
MAK
4 dependents
E2E test — closet save flow + retailer redirect.
A
Engineering
In Progress4
In flight3d
Draft Save-to-Closet spec — edge cases + acceptance criteria.
M
Product Specs
In flight2d
Closet API endpoints — POST /save, GET /closet, DELETE.
A
Engineering /closet
In flight1d
Closet grid layout — Pinterest-style with hover details.
K
Design
In flight4h
Beta launch copy — landing hero + email + app store.
S
Growth
Done3
Save POST handler with idempotency key.
A
Engineering /save
Heart icon spec — saved/unsaved + animation.
K
Design Specs
Affiliate tracker spec — partner cuts, attribution rules.
M
Product Specs
LS
This spec looks solid. One question — do we need a save limit?
M
No limit. Closet is the retention hook — more saves = more return visits. Storage cost is negligible.
LS
Makes sense. What about when a price changes after saving — show the old price or new?
M
Both. Show current price + "was $89 when saved." I've added this as an edge case to the spec.
Spec updated
M
Save to Closet spec