verifylisted

# Stage 6V: Visual & Functional Verification Verify the RUNNING application against every screen specification and acceptance criterion in the PRD by navigating the app in a browser. Lead a multi-agent verification project using Claude Code Agent Teams. Read the detailed guide at `${CLAUDE_SKILL_ROOT}/references/verification-detailed-guide.md` for full teammate prompts, failure patterns, and report templates. Read the scenario generation guide at `${CLAUDE_SKILL_ROOT}/references/feature-scenario-generation.md` for the algorithm to build the Feature Scenario Matrix. ## Prerequisites 1. Verify `./plancasting/_launch/readiness-report.md` exists and shows READY. If NOT READY or file missing, STOP -- run Stage 6H first. 2. Create output directories: ```bash mkdir -p ./plancasting/_audits/visual-verification mkdir -p ./screenshots/automated mkdir -p ./screenshots/criteria mkdir -p ./screenshots/vision mkdir -p ./screenshots/visual-verification/baseline mkdir -p ./e2e/verification ``` 3. Verify Playwright browsers are installed: ```bash bunx playwright install --with-deps chromium ``` ## Scope Modes - **`full`** (default) -- All screens in `plancasting/prd/08-screen-specifications.md`. ~30-60 min. - **`critical`** -- P0/P1 features only. ~15-30 min. - **`diff`** -- Only screens related to files changed since last verification. ~10-20 min. **Note**: `last-verified-commit.txt` is created at the END of a 6V run, so `diff` mode only works on the s