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*
|
||||
Reference in New Issue
Block a user