dialectic
Prove and counter-prove a statement using parallel agents to eliminate confirmation bias. Use when someone says "dialectic", "prove/disprove", "stress test this claim", "is this really true", "argue both sides", or when a statement needs objective analysis from opposing viewpoints.
What this skill does
# Dialectic Analysis Objective analysis of a statement by running two agents with opposing goals in parallel, then synthesizing findings. ## Process ### Step 1: Launch Parallel Agents **CRITICAL: Both Task tool calls MUST be in a single message for true parallel execution.** Do NOT use run_in_background. Do NOT launch sequentially. Foreground agents in the same message run in parallel and block until both complete. **Agent 1 (Thesis)** — find all POSITIVE evidence: - what works well, improvements, correct patterns - supporting facts, proof the statement is TRUE - benefits, strengths, successful outcomes **Agent 2 (Antithesis)** — find all NEGATIVE evidence: - what's problematic, issues, risks, anti-patterns - edge cases, proof the statement is FALSE - weaknesses, failure modes, hidden costs Both agents must provide specific file paths and line numbers when analyzing code. ### Step 2: Synthesize After both agents complete, synthesize findings into an objective conclusion: - weigh evidence from both sides - identify where thesis and antithesis agree (strongest signal) - note unresolved tensions ### Step 3: Verify **CRITICAL** — after presenting the synthesis, verify it against actual implementation: - read the specific files and line numbers referenced by both agents - confirm the evidence cited actually exists in the codebase - check the implementation flow matches the claims made - verify the synthesis accurately reflects the actual code context - identify any misinterpretations or missing context from agent reports - revise synthesis if verification reveals inaccuracies ## Use Cases **Architecture decisions:** ``` /thinking-tools:dialectic this microservice split improves maintainability ``` **Bug analysis:** ``` /thinking-tools:dialectic the connection pool fixes the timeout issue ``` **Performance claims:** ``` /thinking-tools:dialectic caching reduced database load by 80% ``` **Refactoring safety:** ``` /thinking-tools:dialectic extracting this interface simplifies testing ``` **Code review:** ``` /thinking-tools:dialectic this implementation is thread-safe ``` **Review changes:** ``` /thinking-tools:dialectic review the changes in server.go ``` ## Key Principles - **Eliminate confirmation bias** — examining both sides simultaneously prevents anchoring on the first conclusion - **Evidence-based** — agents must cite specific files, lines, and facts, not general claims - **Verification required** — synthesis must be checked against actual code before presenting - **Objective conclusion** — the goal is truth, not winning either side
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.