Version: 1.0
Owner: Product Manager
Last Updated: February 2025
This document defines what to do first for SkillProof in two areas:
| Area | What it covers | Use it when you're… |
|---|---|---|
| Product | Features, epics, and roadmap order (what we build and ship) | Deciding what to build next, planning sprints, saying no to scope. |
| Website | Landing, pages, SEO, and conversion (what we prioritize on the site) | Deciding what to improve on the web presence, marketing, or growth. |
You don’t have to choose one. Use Product priorities for engineering and product decisions; use Website priorities for landing page, SEO, and conversion. Both are in this doc so there’s a single place to look.
Start with Product MVP, in this order. Do not jump to website-only work or post-MVP features until the row you're on is done (or in parallel only when the table says so).
Landing page: Build a minimal landing (hero + "Get verified" / "Find talent") as soon as auth exists so you can drive signups; full landing polish fits in step 10.
Bottom line: Start with step 1 (Project setup & infrastructure). Then do step 2 (Authentication). Then continue in order. After MVP ships, use P1.3 (Post-MVP) and P2 (Website) for what's next.
| Your role or question | Use |
|---|---|
| “What do we build next?” / “What’s in scope for MVP?” | Product (P1). |
| “What do we build after MVP?” | Product (P1.3 — HIGH then MEDIUM then LOW). |
| “What should we fix on the landing / site?” | Website (P2). |
| “Do we focus on product or website first?” | Product first (MVP must work); website landing and auth are part of MVP. So: ship MVP (product + landing + auth), then use P2 to improve site and P1.3 to improve product. |
| Planning a sprint | Product (P1.2) for build order; Website (P2) if the sprint includes landing/SEO/copy. |
| Saying no to a feature | Product (P1.2–1.4): if it’s not P0 for MVP or in HIGH/MEDIUM/LOW, it’s not the current priority. |
Short answer: Use Product for feature and build order; use Website for landing, SEO, and conversion. For “what should I do first?” — ship MVP (product + core website) first, then follow the post-MVP product list and website list above.
| Document | Use |
|---|---|
| PRD.md | MVP scope, features, success metrics. |
| breakdown.txt | Epic and story-level task breakdown; priorities per story. |
| Features.txt | Full list of improvements; P11 = priority ranking. |
| OverView.txt | Phases, roadmap, KPIs. |
| PRODUCT_STYLE_REFERENCE.md | Copy and style for product and key website pages. |
END OF PRIORITY GUIDE
Update when roadmap, MVP scope, or website goals change.