chore: archive v1.2 Collection Power-Ups milestone
Archive roadmap and requirements to milestones/, evolve PROJECT.md with validated requirements, update retrospective, and reorganize ROADMAP.md with milestone groupings. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
128
.planning/milestones/v1.2-REQUIREMENTS.md
Normal file
128
.planning/milestones/v1.2-REQUIREMENTS.md
Normal file
@@ -0,0 +1,128 @@
|
||||
# Requirements Archive: v1.2 Collection Power-Ups
|
||||
|
||||
**Archived:** 2026-03-16
|
||||
**Status:** SHIPPED
|
||||
|
||||
For current requirements, see `.planning/REQUIREMENTS.md`.
|
||||
|
||||
---
|
||||
|
||||
# Requirements: GearBox v1.2 Collection Power-Ups
|
||||
|
||||
**Defined:** 2026-03-16
|
||||
**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.
|
||||
|
||||
## v1.2 Requirements
|
||||
|
||||
Requirements for this milestone. Each maps to roadmap phases.
|
||||
|
||||
### Search & Filter
|
||||
|
||||
- [x] **SRCH-01**: User can search items by name with instant filtering as they type
|
||||
- [x] **SRCH-02**: User can filter collection items by category via dropdown
|
||||
- [x] **SRCH-03**: User can combine text search with category filter simultaneously
|
||||
- [x] **SRCH-04**: User can see result count when filters are active (e.g., "showing 12 of 47 items")
|
||||
- [x] **SRCH-05**: User can clear all active filters with one action
|
||||
|
||||
### Weight Units
|
||||
|
||||
- [x] **UNIT-01**: User can select preferred weight unit (g, oz, lb, kg) from settings
|
||||
- [x] **UNIT-02**: All weight displays across the app reflect the selected unit
|
||||
- [x] **UNIT-03**: Weight unit preference persists across sessions
|
||||
|
||||
### Weight Classification
|
||||
|
||||
- [x] **CLAS-01**: User can classify each item within a setup as base weight, worn, or consumable
|
||||
- [x] **CLAS-02**: Setup totals display base weight, worn weight, consumable weight, and total separately
|
||||
- [x] **CLAS-03**: Items default to "base weight" classification when added to a setup
|
||||
- [x] **CLAS-04**: Same item can have different classifications in different setups
|
||||
|
||||
### Weight Visualization
|
||||
|
||||
- [x] **VIZZ-01**: User can view a donut chart showing weight distribution by category in a setup
|
||||
- [x] **VIZZ-02**: User can toggle chart between category view and classification view (base/worn/consumable)
|
||||
- [x] **VIZZ-03**: User can hover chart segments to see category name, weight, and percentage
|
||||
|
||||
### Candidate Status
|
||||
|
||||
- [x] **CAND-01**: Each candidate displays a status badge (researching, ordered, or arrived)
|
||||
- [x] **CAND-02**: User can change a candidate's status via click interaction
|
||||
- [x] **CAND-03**: New candidates default to "researching" status
|
||||
|
||||
### Planning UI
|
||||
|
||||
- [x] **PLAN-01**: Planning category filter dropdown shows Lucide icons alongside category names
|
||||
|
||||
## Future Requirements
|
||||
|
||||
Deferred to future milestones. Tracked but not in current roadmap.
|
||||
|
||||
### Planning Enhancements
|
||||
|
||||
- **COMP-01**: User can compare candidates side-by-side on weight and price
|
||||
- **RANK-01**: User can rank/prioritize candidates within a thread
|
||||
- **IMPC-01**: User can preview how a candidate affects setup weight/cost before resolving
|
||||
|
||||
### Data Management
|
||||
|
||||
- **DATA-01**: User can import gear collection from CSV
|
||||
- **DATA-02**: User can export gear collection to CSV
|
||||
|
||||
### Social & Multi-User
|
||||
|
||||
- **SOCL-01**: User can create an account with authentication
|
||||
- **SOCL-02**: User can share collections and setups publicly
|
||||
- **SOCL-03**: User can view other users' public profiles and setups
|
||||
|
||||
### Automation
|
||||
|
||||
- **AUTO-01**: System can auto-fill product information (price, weight, images) from external sources
|
||||
|
||||
## Out of Scope
|
||||
|
||||
Explicitly excluded. Documented to prevent scope creep.
|
||||
|
||||
| Feature | Reason |
|
||||
|---------|--------|
|
||||
| Per-item weight input in multiple units | Parsing complexity, ambiguous storage -- display-only conversion is sufficient |
|
||||
| Interactive chart drill-down (click to zoom) | Adds significant interaction complexity for minimal value |
|
||||
| Weight goals / targets | Opinionated norms conflict with hobby-agnostic design |
|
||||
| Custom classification labels | base/worn/consumable covers 95% of use cases |
|
||||
| Server-side full-text search | Premature for single-user app with <1000 items |
|
||||
| Classification at item level (not setup level) | Same item has different roles in different setups |
|
||||
| Status change timestamps | Useful but adds schema complexity -- defer |
|
||||
|
||||
## Traceability
|
||||
|
||||
Which phases cover which requirements. Updated during roadmap creation.
|
||||
|
||||
| Requirement | Phase | Status |
|
||||
|-------------|-------|--------|
|
||||
| SRCH-01 | Phase 8 | Complete |
|
||||
| SRCH-02 | Phase 8 | Complete |
|
||||
| SRCH-03 | Phase 8 | Complete |
|
||||
| SRCH-04 | Phase 8 | Complete |
|
||||
| SRCH-05 | Phase 8 | Complete |
|
||||
| UNIT-01 | Phase 7 | Complete |
|
||||
| UNIT-02 | Phase 7 | Complete |
|
||||
| UNIT-03 | Phase 7 | Complete |
|
||||
| CLAS-01 | Phase 9 | Complete |
|
||||
| CLAS-02 | Phase 9 | Complete |
|
||||
| CLAS-03 | Phase 9 | Complete |
|
||||
| CLAS-04 | Phase 9 | Complete |
|
||||
| VIZZ-01 | Phase 9 | Complete |
|
||||
| VIZZ-02 | Phase 9 | Complete |
|
||||
| VIZZ-03 | Phase 9 | Complete |
|
||||
| CAND-01 | Phase 8 | Complete |
|
||||
| CAND-02 | Phase 8 | Complete |
|
||||
| CAND-03 | Phase 8 | Complete |
|
||||
| PLAN-01 | Phase 8 | Complete |
|
||||
|
||||
**Coverage:**
|
||||
- v1.2 requirements: 19 total
|
||||
- Mapped to phases: 19
|
||||
- Unmapped: 0
|
||||
|
||||
---
|
||||
*Requirements defined: 2026-03-16*
|
||||
*Last updated: 2026-03-16 after roadmap creation*
|
||||
98
.planning/milestones/v1.2-ROADMAP.md
Normal file
98
.planning/milestones/v1.2-ROADMAP.md
Normal file
@@ -0,0 +1,98 @@
|
||||
# Roadmap: GearBox
|
||||
|
||||
## Milestones
|
||||
|
||||
- v1.0 MVP -- Phases 1-3 (shipped 2026-03-15)
|
||||
- v1.1 Fixes & Polish -- Phases 4-6 (shipped 2026-03-15)
|
||||
- **v1.2 Collection Power-Ups** -- Phases 7-9 (in progress)
|
||||
|
||||
## Phases
|
||||
|
||||
<details>
|
||||
<summary>v1.0 MVP (Phases 1-3) -- SHIPPED 2026-03-15</summary>
|
||||
|
||||
- [x] Phase 1: Foundation and Collection (4/4 plans) -- completed 2026-03-14
|
||||
- [x] Phase 2: Planning Threads (3/3 plans) -- completed 2026-03-15
|
||||
- [x] Phase 3: Setups and Dashboard (3/3 plans) -- completed 2026-03-15
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>v1.1 Fixes & Polish (Phases 4-6) -- SHIPPED 2026-03-15</summary>
|
||||
|
||||
- [x] Phase 4: Database & Planning Fixes (2/2 plans) -- completed 2026-03-15
|
||||
- [x] Phase 5: Image Handling (2/2 plans) -- completed 2026-03-15
|
||||
- [x] Phase 6: Category Icons (3/3 plans) -- completed 2026-03-15
|
||||
|
||||
</details>
|
||||
|
||||
### v1.2 Collection Power-Ups (In Progress)
|
||||
|
||||
**Milestone Goal:** Make core gear management significantly more useful as collections grow -- better search, proper weight classification, richer planning threads.
|
||||
|
||||
- [x] **Phase 7: Weight Unit Selection** - Users see all weights in their preferred unit across the entire app
|
||||
- [x] **Phase 8: Search, Filter, and Candidate Status** - Users can find items quickly and track candidate purchase progress
|
||||
- [x] **Phase 9: Weight Classification and Visualization** - Users can classify gear by role and visualize weight distribution in setups
|
||||
|
||||
## Phase Details
|
||||
|
||||
### Phase 7: Weight Unit Selection
|
||||
**Goal**: Users see all weights in their preferred unit across the entire app
|
||||
**Depends on**: Nothing (first phase of v1.2)
|
||||
**Requirements**: UNIT-01, UNIT-02, UNIT-03
|
||||
**Success Criteria** (what must be TRUE):
|
||||
1. User can select a weight unit (g, oz, lb, kg) from a visible control and the selection persists after closing and reopening the app
|
||||
2. Every weight value in the app (item cards, candidate cards, category headers, totals bar, setup details) displays in the selected unit with appropriate precision
|
||||
3. Weight input fields accept values and store them correctly regardless of display unit (no rounding drift across edit cycles)
|
||||
**Plans:** 2 plans
|
||||
|
||||
Plans:
|
||||
- [x] 07-01-PLAN.md -- TDD formatWeight unit conversion core + useWeightUnit hook
|
||||
- [ ] 07-02-PLAN.md -- Wire unit toggle into TotalsBar and update all 8 call sites
|
||||
|
||||
### Phase 8: Search, Filter, and Candidate Status
|
||||
**Goal**: Users can find items quickly and track candidate purchase progress
|
||||
**Depends on**: Phase 7
|
||||
**Requirements**: SRCH-01, SRCH-02, SRCH-03, SRCH-04, SRCH-05, PLAN-01, CAND-01, CAND-02, CAND-03
|
||||
**Success Criteria** (what must be TRUE):
|
||||
1. User can type in a search field on the collection page and see items filtered instantly by name as they type
|
||||
2. User can select a category from a dropdown (showing Lucide icons alongside names) to filter items in both collection and planning views
|
||||
3. User can see how many items match active filters (e.g., "showing 12 of 47 items") and clear all filters with one action
|
||||
4. Each candidate in a planning thread displays a status badge (researching, ordered, or arrived) that the user can change by clicking
|
||||
5. New candidates automatically start with "researching" status
|
||||
**Plans:** 2 plans
|
||||
|
||||
Plans:
|
||||
- [ ] 08-01-PLAN.md -- Candidate status vertical slice (schema migration, service, tests, StatusBadge UI)
|
||||
- [ ] 08-02-PLAN.md -- Search/filter toolbar with CategoryFilterDropdown on gear and planning tabs
|
||||
|
||||
### Phase 9: Weight Classification and Visualization
|
||||
**Goal**: Users can classify gear by role and visualize weight distribution in setups
|
||||
**Depends on**: Phase 7, Phase 8
|
||||
**Requirements**: CLAS-01, CLAS-02, CLAS-03, CLAS-04, VIZZ-01, VIZZ-02, VIZZ-03
|
||||
**Success Criteria** (what must be TRUE):
|
||||
1. User can classify each item within a setup as base weight, worn, or consumable, and the same item can have different classifications in different setups
|
||||
2. Setup detail view shows separate weight subtotals for base weight, worn weight, and consumable weight in addition to the overall total
|
||||
3. User can view a donut chart in a setup showing weight distribution, and toggle between category breakdown and classification breakdown
|
||||
4. User can hover chart segments to see the category/classification name, weight (in selected unit), and percentage
|
||||
**Plans:** 2 plans
|
||||
|
||||
Plans:
|
||||
- [ ] 09-01-PLAN.md -- Classification vertical slice (schema, service, tests, API route, ClassificationBadge UI)
|
||||
- [ ] 09-02-PLAN.md -- WeightSummaryCard with subtotals, donut chart, pill toggle, and visual verification
|
||||
|
||||
## Progress
|
||||
|
||||
**Execution Order:** Phase 7 -> Phase 8 -> Phase 9
|
||||
|
||||
| Phase | Milestone | Plans Complete | Status | Completed |
|
||||
|-------|-----------|----------------|--------|-----------|
|
||||
| 1. Foundation and Collection | v1.0 | 4/4 | Complete | 2026-03-14 |
|
||||
| 2. Planning Threads | v1.0 | 3/3 | Complete | 2026-03-15 |
|
||||
| 3. Setups and Dashboard | v1.0 | 3/3 | Complete | 2026-03-15 |
|
||||
| 4. Database & Planning Fixes | v1.1 | 2/2 | Complete | 2026-03-15 |
|
||||
| 5. Image Handling | v1.1 | 2/2 | Complete | 2026-03-15 |
|
||||
| 6. Category Icons | v1.1 | 3/3 | Complete | 2026-03-15 |
|
||||
| 7. Weight Unit Selection | v1.2 | 2/2 | Complete | 2026-03-16 |
|
||||
| 8. Search, Filter, and Candidate Status | v1.2 | 2/2 | Complete | 2026-03-16 |
|
||||
| 9. Weight Classification and Visualization | v1.2 | 2/2 | Complete | 2026-03-16 |
|
||||
Reference in New Issue
Block a user