111 lines
4.3 KiB
Markdown
111 lines
4.3 KiB
Markdown
---
|
|
phase: 02-planning-threads
|
|
plan: 03
|
|
type: execute
|
|
wave: 3
|
|
depends_on: [02-02]
|
|
files_modified: []
|
|
autonomous: false
|
|
requirements: [THRD-01, THRD-02, THRD-03, THRD-04]
|
|
|
|
must_haves:
|
|
truths:
|
|
- "User can create a planning thread and see it in the list"
|
|
- "User can add candidates with weight, price, category, notes, and product link"
|
|
- "User can edit and remove candidates"
|
|
- "User can resolve a thread by picking a winner that appears in their collection"
|
|
artifacts: []
|
|
key_links: []
|
|
---
|
|
|
|
<objective>
|
|
Visual verification of the complete planning threads feature. Confirm all user-facing behaviors work end-to-end in the browser.
|
|
|
|
Purpose: Catch visual, interaction, and integration issues that automated tests cannot detect.
|
|
|
|
Output: Confirmation that Phase 2 requirements are met from the user's perspective.
|
|
</objective>
|
|
|
|
<execution_context>
|
|
@/home/jean-luc-makiola/.claude/get-shit-done/workflows/execute-plan.md
|
|
@/home/jean-luc-makiola/.claude/get-shit-done/templates/summary.md
|
|
</execution_context>
|
|
|
|
<context>
|
|
@.planning/ROADMAP.md
|
|
@.planning/phases/02-planning-threads/02-CONTEXT.md
|
|
@.planning/phases/02-planning-threads/02-01-SUMMARY.md
|
|
@.planning/phases/02-planning-threads/02-02-SUMMARY.md
|
|
</context>
|
|
|
|
<tasks>
|
|
|
|
<task type="checkpoint:human-verify" gate="blocking">
|
|
<name>Task 1: Visual verification of complete planning threads feature</name>
|
|
<files></files>
|
|
<action>
|
|
Verify the complete planning threads feature in the browser.
|
|
|
|
What was built: Tab navigation between My Gear and Planning views, thread CRUD with card-based list, candidate CRUD with slide-out panel, and thread resolution flow with confirmation dialog.
|
|
|
|
Start the dev server if not running: `bun run dev`
|
|
Open http://localhost:5173
|
|
|
|
**1. Tab Navigation (THRD-01)**
|
|
- Verify "My Gear" and "Planning" tabs are visible
|
|
- Click "Planning" tab -- URL should update to /?tab=planning
|
|
- Click "My Gear" tab -- should show your gear collection
|
|
- Verify top navigation bar is always visible
|
|
|
|
**2. Thread Creation (THRD-01)**
|
|
- On the Planning tab, create a new thread (e.g. "Helmet")
|
|
- Verify it appears as a card in the thread list
|
|
- Card should show: name, "0 candidates", creation date
|
|
- Create a second thread to verify list ordering (most recent first)
|
|
|
|
**3. Candidate Management (THRD-02, THRD-03)**
|
|
- Click a thread card to open thread detail page
|
|
- Verify back navigation to Planning tab works
|
|
- Add a candidate via slide-out panel with: name, weight, price, category, notes, product URL
|
|
- Verify candidate appears as a card in the grid
|
|
- Add 2-3 more candidates with different prices
|
|
- Verify the thread card on the list page shows updated candidate count and price range
|
|
- Edit a candidate (change price or name) -- verify changes saved
|
|
- Delete a candidate -- verify confirmation dialog and removal
|
|
|
|
**4. Thread Resolution (THRD-04)**
|
|
- On a thread with multiple candidates, click "Pick Winner" on one
|
|
- Verify confirmation dialog: "Pick [X] as winner? This will add it to your collection."
|
|
- Confirm the resolution
|
|
- Verify thread disappears from active thread list
|
|
- Toggle "Show archived" -- verify resolved thread appears (visually distinct)
|
|
- Switch to "My Gear" tab -- verify the winning candidate appears as a new collection item with correct data
|
|
|
|
**5. Visual Consistency**
|
|
- Thread cards match the visual style of item cards (same shadows, rounded corners)
|
|
- Candidate cards match item card style
|
|
- Pill/chip tags are consistent with existing tag pattern
|
|
- Slide-out panel for candidates looks like the item panel
|
|
- Empty states are present and helpful
|
|
</action>
|
|
<verify>User confirms all checks pass by typing "approved"</verify>
|
|
<done>All four THRD requirements verified by user in browser. Visual consistency confirmed. Resolution flow works end-to-end.</done>
|
|
</task>
|
|
|
|
</tasks>
|
|
|
|
<verification>
|
|
User confirms all four THRD requirements work visually and interactively.
|
|
</verification>
|
|
|
|
<success_criteria>
|
|
- All four THRD requirements verified by user in browser
|
|
- Visual consistency with Phase 1 collection UI
|
|
- Resolution flow creates item and archives thread correctly
|
|
- No regressions to existing gear collection functionality
|
|
</success_criteria>
|
|
|
|
<output>
|
|
After completion, create `.planning/phases/02-planning-threads/02-03-SUMMARY.md`
|
|
</output>
|