docs: create roadmap (3 phases)
This commit is contained in:
@@ -74,24 +74,24 @@ Which phases cover which requirements. Updated during roadmap creation.
|
||||
|
||||
| Requirement | Phase | Status |
|
||||
|-------------|-------|--------|
|
||||
| COLL-01 | — | Pending |
|
||||
| COLL-02 | — | Pending |
|
||||
| COLL-03 | — | Pending |
|
||||
| COLL-04 | — | Pending |
|
||||
| THRD-01 | — | Pending |
|
||||
| THRD-02 | — | Pending |
|
||||
| THRD-03 | — | Pending |
|
||||
| THRD-04 | — | Pending |
|
||||
| SETP-01 | — | Pending |
|
||||
| SETP-02 | — | Pending |
|
||||
| SETP-03 | — | Pending |
|
||||
| DASH-01 | — | Pending |
|
||||
| COLL-01 | Phase 1 | Pending |
|
||||
| COLL-02 | Phase 1 | Pending |
|
||||
| COLL-03 | Phase 1 | Pending |
|
||||
| COLL-04 | Phase 1 | Pending |
|
||||
| THRD-01 | Phase 2 | Pending |
|
||||
| THRD-02 | Phase 2 | Pending |
|
||||
| THRD-03 | Phase 2 | Pending |
|
||||
| THRD-04 | Phase 2 | Pending |
|
||||
| SETP-01 | Phase 3 | Pending |
|
||||
| SETP-02 | Phase 3 | Pending |
|
||||
| SETP-03 | Phase 3 | Pending |
|
||||
| DASH-01 | Phase 3 | Pending |
|
||||
|
||||
**Coverage:**
|
||||
- v1 requirements: 12 total
|
||||
- Mapped to phases: 0
|
||||
- Unmapped: 12 ⚠️
|
||||
- Mapped to phases: 12
|
||||
- Unmapped: 0
|
||||
|
||||
---
|
||||
*Requirements defined: 2026-03-14*
|
||||
*Last updated: 2026-03-14 after initial definition*
|
||||
*Last updated: 2026-03-14 after roadmap creation*
|
||||
|
||||
76
.planning/ROADMAP.md
Normal file
76
.planning/ROADMAP.md
Normal file
@@ -0,0 +1,76 @@
|
||||
# Roadmap: GearBox
|
||||
|
||||
## Overview
|
||||
|
||||
GearBox delivers a gear management and purchase planning web app in three phases. Phase 1 establishes the foundation and builds the complete gear collection feature — the core entity everything else depends on. Phase 2 adds planning threads, the product's differentiator, enabling structured purchase research with candidate comparison and thread resolution into the collection. Phase 3 completes the app with named setups (loadouts composed from collection items) and the dashboard home page that ties everything together.
|
||||
|
||||
## Phases
|
||||
|
||||
**Phase Numbering:**
|
||||
- Integer phases (1, 2, 3): Planned milestone work
|
||||
- Decimal phases (2.1, 2.2): Urgent insertions (marked with INSERTED)
|
||||
|
||||
Decimal phases appear between their surrounding integers in numeric order.
|
||||
|
||||
- [ ] **Phase 1: Foundation and Collection** - Project scaffolding, data model, and complete gear item CRUD with categories and totals
|
||||
- [ ] **Phase 2: Planning Threads** - Purchase research workflow with candidates, comparison, and thread resolution
|
||||
- [ ] **Phase 3: Setups and Dashboard** - Named loadouts from collection items and dashboard home page
|
||||
|
||||
## Phase Details
|
||||
|
||||
### Phase 1: Foundation and Collection
|
||||
**Goal**: Users can catalog their gear collection with full item details, organize by category, and see aggregate weight and cost totals
|
||||
**Depends on**: Nothing (first phase)
|
||||
**Requirements**: COLL-01, COLL-02, COLL-03, COLL-04
|
||||
**Success Criteria** (what must be TRUE):
|
||||
1. User can add a gear item with name, weight, price, category, notes, and product link and see it in their collection
|
||||
2. User can edit any field on an existing item and delete items they no longer want
|
||||
3. User can create, rename, and delete categories, and every item belongs to a user-defined category
|
||||
4. User can see automatic weight and cost totals per category and for the entire collection
|
||||
5. The app runs as a single Bun process with SQLite storage and serves a clean, minimalist UI
|
||||
**Plans**: TBD
|
||||
|
||||
Plans:
|
||||
- [ ] 01-01: TBD
|
||||
- [ ] 01-02: TBD
|
||||
|
||||
### Phase 2: Planning Threads
|
||||
**Goal**: Users can research potential purchases through planning threads — adding candidates, comparing them, and resolving a thread by picking a winner that moves into their collection
|
||||
**Depends on**: Phase 1
|
||||
**Requirements**: THRD-01, THRD-02, THRD-03, THRD-04
|
||||
**Success Criteria** (what must be TRUE):
|
||||
1. User can create a planning thread with a descriptive name and see it in a threads list
|
||||
2. User can add candidate products to a thread with weight, price, notes, and product link
|
||||
3. User can edit and remove candidates from an active thread
|
||||
4. User can resolve a thread by selecting a winning candidate, which automatically creates a new item in their collection and archives the thread
|
||||
**Plans**: TBD
|
||||
|
||||
Plans:
|
||||
- [ ] 02-01: TBD
|
||||
- [ ] 02-02: TBD
|
||||
|
||||
### Phase 3: Setups and Dashboard
|
||||
**Goal**: Users can compose named loadouts from their collection items with live totals, and navigate the app through a dashboard home page
|
||||
**Depends on**: Phase 1, Phase 2
|
||||
**Requirements**: SETP-01, SETP-02, SETP-03, DASH-01
|
||||
**Success Criteria** (what must be TRUE):
|
||||
1. User can create a named setup (e.g. "Summer Bikepacking") and see it in a setups list
|
||||
2. User can add and remove collection items from a setup
|
||||
3. User can see total weight and cost for a setup, computed live from current item data
|
||||
4. User sees a dashboard home page with cards linking to their collection, active threads, and setups
|
||||
**Plans**: TBD
|
||||
|
||||
Plans:
|
||||
- [ ] 03-01: TBD
|
||||
- [ ] 03-02: TBD
|
||||
|
||||
## Progress
|
||||
|
||||
**Execution Order:**
|
||||
Phases execute in numeric order: 1 -> 2 -> 3
|
||||
|
||||
| Phase | Plans Complete | Status | Completed |
|
||||
|-------|----------------|--------|-----------|
|
||||
| 1. Foundation and Collection | 0/0 | Not started | - |
|
||||
| 2. Planning Threads | 0/0 | Not started | - |
|
||||
| 3. Setups and Dashboard | 0/0 | Not started | - |
|
||||
61
.planning/STATE.md
Normal file
61
.planning/STATE.md
Normal file
@@ -0,0 +1,61 @@
|
||||
# Project State
|
||||
|
||||
## Project Reference
|
||||
|
||||
See: .planning/PROJECT.md (updated 2026-03-14)
|
||||
|
||||
**Core value:** Make it effortless to manage gear and plan new purchases — see how a potential buy affects your total setup weight and cost before committing.
|
||||
**Current focus:** Phase 1: Foundation and Collection
|
||||
|
||||
## Current Position
|
||||
|
||||
Phase: 1 of 3 (Foundation and Collection)
|
||||
Plan: 0 of 0 in current phase
|
||||
Status: Ready to plan
|
||||
Last activity: 2026-03-14 — Roadmap created
|
||||
|
||||
Progress: [░░░░░░░░░░] 0%
|
||||
|
||||
## Performance Metrics
|
||||
|
||||
**Velocity:**
|
||||
- Total plans completed: 0
|
||||
- Average duration: -
|
||||
- Total execution time: 0 hours
|
||||
|
||||
**By Phase:**
|
||||
|
||||
| Phase | Plans | Total | Avg/Plan |
|
||||
|-------|-------|-------|----------|
|
||||
| - | - | - | - |
|
||||
|
||||
**Recent Trend:**
|
||||
- Last 5 plans: -
|
||||
- Trend: -
|
||||
|
||||
*Updated after each plan completion*
|
||||
|
||||
## Accumulated Context
|
||||
|
||||
### Decisions
|
||||
|
||||
Decisions are logged in PROJECT.md Key Decisions table.
|
||||
Recent decisions affecting current work:
|
||||
|
||||
- [Roadmap]: 3-phase coarse structure — Collection, Threads, Setups+Dashboard
|
||||
- [Roadmap]: Setups and Dashboard combined into single phase (coarse granularity)
|
||||
|
||||
### Pending Todos
|
||||
|
||||
None yet.
|
||||
|
||||
### Blockers/Concerns
|
||||
|
||||
- Verify @hono/zod-validator supports Zod 4.x before starting Phase 1. If not, pin Zod 3.23.x.
|
||||
- Confirm Bun fullstack vs. Vite proxy dev setup pattern before project scaffolding.
|
||||
|
||||
## Session Continuity
|
||||
|
||||
Last session: 2026-03-14
|
||||
Stopped at: Roadmap created, ready to plan Phase 1
|
||||
Resume file: None
|
||||
Reference in New Issue
Block a user