feature-validationlisted

# Feature Validation ## 🚨 CRITICAL BLOCKERS - READ FIRST **This skill has TWO mandatory file reads that CANNOT be skipped:** 1. **Phase 1 BLOCKER:** You MUST read the session transcript from `C:\Users\pauol\.claude\projects\G---OneDrive-OneDrive-Desktop\{session_id}.jsonl` to identify the trigger message. Find the most recent `.jsonl` file and document the user message that invoked this skill. 2. **Phase 10 BLOCKER:** You MUST re-read the session transcript to perform an evidence-based retrospective. Cite specific line numbers. In-context memory is NOT sufficient. **Session transcript location:** `C:\Users\pauol\.claude\projects\G---OneDrive-OneDrive-Desktop\` **If you cannot read the transcript:** STOP and inform the user. Do not proceed with memory-based retrospective. --- ## Overview **Feature validation is REAL testing, not documentation screenshots.** This skill ensures implemented features are tested by actually navigating to the app, interacting with elements, checking console errors, and validating functionality works as intended. **Core principle:** If you didn't interact with the real feature in the real app, you didn't test it. ## When to Use - After completing a feature implementation phase - After fixing bugs that need verification - After any CRUD-related changes - When user requests validation of recent work - Before marking any implementation as "complete" **Do NOT use for:** - Unit test writing (use test-driven-development skill) - Code review (