← ClaudeAtlas

discrepancies-fixlisted

Classifies and resolves contradictions between requirements, designs, API contracts, and actual system behaviour, auto-closing the unambiguous ones by source-priority rules and escalating real defects to the engineer with a ready-made bug report. Use this skill whenever requirements and design disagree, whenever a generated test fails because the system behaves differently from the spec, whenever the user asks "is this a bug or is the requirement wrong", or as the reconciliation stage of the QA pipeline. Also use it to turn a confirmed discrepancy into a properly structured defect ticket.
YevheniiaQA/qa-agent-toolkit · ★ 0 · Testing & QA · score 72
Install: claude install-skill YevheniiaQA/qa-agent-toolkit
# Discrepancies Fix Every pipeline stage that compares two sources of truth appends its findings to one protocol file. This skill owns that file: classify, resolve what is unambiguous, escalate what is not. ## Disabled integrations Follow `qa-conventions` → *Disabled integrations* for the defect tracker (`jira`, `linear`): read `INTEGRATIONS`, skip a system that is not listed, report it as `➖ <system> disabled for this project`, never route around a `qa-guard` block. **Local alternative:** when the tracker is disabled, or the profile says `DEFECT_SINK=local`, "file a bug" means writing `bugs/<id>.md` in the workspace with the template below. The one-confirmation-per-ticket rule still applies to anything that leaves the workspace. ## The protocol file All skills append to `02-analysis/<TICKET-ID>/DISCREPANCIES.md`: ```markdown ### D-007 — FIGMA_REQ_MISMATCH — open - **Where**: US-001, delete-folder confirmation dialog - **Requirements say**: single string "Deleting the folder moves all chats to archive. Delete folder?" - **Figma shows**: title "Delete folder?" + body "Deleting the folder moves all chats to archive." - **Affects**: TC-283-UI-009 - **Detected by**: figma-analyzer, 2026-03-11 ``` ## Classification | Type | Meaning | Auto-closable | |---|---|---| | `FIGMA_REQ_MISMATCH` | Design and written requirement differ on a UI detail | Yes — design wins for UI presentation | | `CONTRACT_REQ_MISMATCH` | API spec and requirement text differ | Yes — code-derived contra