Compare provided documentation against actual codebase implementation. Output is a structured diff of claims vs reality. Do NOT rewrite the docs. Do NOT suggest wording. Just report discrepancies. User provides documentation to verify (text, file, or URL) Identify the feature/aspect being documented Parse the documentation into discrete claims Tag each claim with a category (behavior, config, constraint, etc.) Record the exact quote from the documentation For each claim, find the relevant code Compare claim to actual implementation Record: ACCURATE, INACCURATE, OUTDATED, MISSING_CONTEXT, or UNVERIFIABLE For inaccuracies, record what the code actually does Write verification to .roo/extraction/VERIFY-[feature].yaml Use the output schema (see output_format.xml) Claim matches implementation Claim contradicts implementation What the code actually does Claim was once true but code has changed Current behavior Claim is true but omits important information The missing context Cannot find code to verify this claim Search paths attempted behavior configuration constraint error_handling ui integration prerequisite Verify facts, not writing quality Report what code does, not what docs should say Include source file paths as evidence Do NOT suggest documentation rewrites Do NOT evaluate if docs are "good" - only if they're accurate Quote exact code when showing discrepancies