trust-but-verify
Trust But Verify
Apply skeptical verification to all system claims, test results, and assumptions through independent validation rather than blind trust, preventing false confidence and accelerating issue detection.
When to use me
Use this skill when:
- Tests pass but you suspect something might still be wrong
- Documentation claims features work but you want to verify
- System memory/brain/progress tracking says something is built
- Stakeholders assume functionality exists based on reports
- You need to validate assumptions before critical decisions
- Building resilience against false positives and blind spots
- Preparing for production releases or high-risk changes
- Onboarding to a system with uncertain quality signals
What I do
1. Claim Identification
More from wojons/skills
adversarial-thinking
Apply systematic adversarial thinking patterns including devil's advocate, assumption busting, red teaming, and white hat security approaches
45devils-advocate
Challenge ideas, assumptions, and decisions by playing devil's advocate to identify weaknesses and prevent groupthink
41redteam
Think and act like an attacker to identify security vulnerabilities, weaknesses, and penetration vectors through adversarial security testing
37code-migration
Guide framework and library migrations with incremental strategies, breaking change analysis, compatibility testing, and automated migration tools
35observability-logging
Use logs as part of comprehensive observability strategy including metrics, traces, alerts, and dashboards for system understanding and operational excellence
34white-hat
Build defensive security capabilities, implement security by design, and practice ethical hacking to protect systems proactively
34