gza-spec-reviewlisted

# Gza Spec Review Run an interactive quality gate for a specific spec file before implementation starts. ## Inputs - Required: path to a spec file (e.g. `specs/foo.md`) If the user did not provide a spec path, ask for it before proceeding. Normalize spec paths: - If input is just a filename like `foo.md`, expand to `specs/foo.md` - If the file does not exist, stop and report the error ## Process ### Step 1: Read and understand the spec Read the spec file in full. Identify: - The core problem/feature being described - Concrete claims: file paths, command names, config fields, function signatures, workflow steps - Acceptance criteria (explicit or implied) - Dependencies on other specs, tasks, or systems ### Step 2: Verify claims against the codebase For each concrete claim in the spec: 1. **File paths** - Does the spec reference files that exist? - Search with Glob for referenced paths - Flag paths that don't exist and aren't plausible future additions 2. **Command/option names** - Does the spec describe CLI commands or flags? - Compare against `uv run gza --help` and `uv run gza <command> --help` - Flag commands that were renamed or flags that changed 3. **Config fields** - Does the spec reference configuration options? - Search `src/gza/config.py` for referenced field names - Flag fields that were renamed or removed 4. **Code patterns** - Does the spec describe specific functions, classes, or modules? - Search with Grep for referenced identi