spec-reviewlisted

# OpenSpec Verification Guide for verifying that implementation matches spec artifacts. ## Input Files | File | Required | Purpose | |------|----------|---------| | `{specs_path}/design.md` | Yes | Requirements and scenarios to verify | | `{specs_path}/tasks.md` | Yes | Completion checklist | | `{specs_path}/proposal.md` | Optional | Original intent reference | **Path Enforcement**: The `specs_path` MUST be `.scaffolding/conversations/{UUID}/specs/` where `{UUID}` is a valid UUID (format: `xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`). NEVER use descriptive folder names. ## Three Verification Dimensions ### 1. Completeness **Question**: Are all tasks done and all requirements covered? | Check | Method | Issue Level | |-------|--------|-------------| | All checkboxes marked `[x]` | Parse tasks.md | CRITICAL if incomplete | | All requirements have code | Search codebase for keywords | CRITICAL if missing | | All new files exist | Verify file paths from tasks | CRITICAL if missing | ### 2. Correctness **Question**: Does the code do what the spec says? | Check | Method | Issue Level | |-------|--------|-------------| | GIVEN/WHEN/THEN satisfied | Trace scenario through code | WARNING if divergent | | Tests cover scenarios | Match test names to scenarios | WARNING if uncovered | | Edge cases handled | Check error paths in code | WARNING if missing | | Validation commands pass | Run pytest / npm run validate | CRITICAL if failing | ### 3. Coherence **Question**: Does the code