evidence-based-developmentlisted

# Evidence-Based Development Foundation skill that governs how Claude gathers, presents, and acts on evidence during development. ## Iron Law **EVIDENCE BEFORE CLAIMS, ALWAYS. If you haven't read the code, you don't know what it does.** This is non-negotiable. No recommendation without a citation. No behavioral claim without verification. Confidence is not evidence. ## Show Before Decide Never propose a change without first showing the current state. Read the file, cite the line, then suggest. **Pattern**: "Here's what I found at `file.rb:42` → here's what I recommend → here's why." ## Citation Requirements Every claim about code must include a file:line reference. No exceptions. - Use `file_path:line_number` format in all findings - When reviewing diffs, cite both the file and the specific hunk - When reporting issues, show the exact code snippet as evidence ## Finding Prioritization All findings, review comments, and issues use P1/P2/P3 classification. This priority system operationalizes the organizational hard boundary **"No Ungrounded Claims"** — every finding must carry evidence (file:line citation, test output, runtime observation) proportional to its priority, and no recommendation may be made without verification against current sources. | Priority | Meaning | Action | |----------|---------|--------| | **P1** | Must fix — blocks merge, security issue, data loss risk, broken functionality | Fix before proceeding | | **P2** | Should fix — logic error, miss