speckit-validatelisted

## User Input ```text $ARGUMENTS ``` ## Outline Deterministically verify that the implementation matches the specification by checking task completion, file existence, and requirement traceability. ### Step 1: Select feature If `$ARGUMENTS` specifies a feature name or number, use that. Otherwise, find the most recently modified feature in `specs/`. If no features exist, error: "No features found in specs/. Run `/speckit.specify` first." ### Step 2: Parse tasks Read `tasks.md` from the feature directory. Parse each checkbox line: - Extract task text (after `- [x]` or `- [ ]`) - Mark as completed or remaining - Extract keywords: file paths (`auth/login.py`), snake_case names (`user_auth`), CamelCase names (`UserAuth`), dotted names (`config.yaml`) If no `tasks.md` exists, error: "No tasks.md found. Run `/speckit.tasks` first." ### Step 3: Verify completed task artifacts For each completed task that references file paths: 1. Search the project directory for the referenced file 2. If found: PASS 3. If not found: WARN ("task says 'Create auth/login.py' but file not found") Skip verification for: - Incomplete tasks (not yet implemented) - Tasks with no file path references (e.g., "Set up CI pipeline") ### Step 4: Parse spec requirements Read `spec.md` from the feature directory. Extract items from the "Functional Requirements" section (bulleted list items under that heading). If no requirements section found, skip to Step 6. ### Step 5: Trace requirements to tasks