plugins/market-research/skills/analyzing-contradictions/SKILL.md
Detect gaps and contradictions across all prior phases; surface cross-phase tensions, unresolved assumptions, and sales/investor objections. Run after `developing-gtm-strategy` (Phase 4).
npx skillsauth add qte77/claude-code-plugins analyzing-contradictionsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Target: $ARGUMENTS
Phase 4 of the GTM pipeline. Depends on Phase 3. Reviews all prior phase outputs for internal contradictions, unresolved tensions, and gaps that could undermine the GTM strategy.
Read config/mode.md before starting:
concise — Top 3 contradictions + top 5 objections (brief)detailed — Full contradiction register, root cause analysis, resolution roadmapconservative — Surface all contradictions regardless of severity; prefer resolution over ignoringambitious — Frame contradictions as opportunities; propose bold resolutionsresults/phase-0/capability-profile.mdresults/phase-1a/competitor-map.mdresults/phase-1b/market-analysis.mdresults/phase-2/pmf-assessment.mdresults/phase-3/gtm-strategy.mdconfig/mode.md — Style and approach settingsconfig/validation_criteria.md Phase 4 gatesWrite to results/phase-4/:
contradiction-analysis.md# Contradiction Analysis
## Cross-Phase Contradictions
### Contradiction 1: [Short description]
- Phases involved: [e.g. Phase 0 vs Phase 3]
- Tension: [What conflicts with what]
- Root cause: [Why this contradiction exists]
- Resolution: [Recommended fix or clarification needed]
- Priority: [High/Medium/Low]
## Assumption Gaps
| Assumption | Phase | Evidence | Gap |
|-----------|-------|----------|-----|
| [assumption] | [phase] | [present/missing] | [what's needed] |
## Objection Register
### Investor Objections
1. "[Objection]" — Response: [recommended response]
### Buyer Objections
1. "[Objection]" — Response: [recommended response]
## Summary
[Overall assessment: pipeline integrity score H/M/L, key blockers before Phase 5]
development
Verify an external or AI-generated security report against the actual codebase before acting on it. Use when handed a scanner PDF, automated teardown, audit report, or bug-bounty submission — classifies every finding CONFIRMED / OVERSTATED / FALSE-POSITIVE / FABRICATED and salvages the real work items.
development
Audits a site's SEO and AI-search (GEO) readiness — meta tags, Open Graph/Twitter, JSON-LD, robots/llms conventions — and generates fixes. Use when reviewing search visibility, social previews, structured data, or LLM/AI-crawler discoverability.
documentation
Generate or update README.md files across three scopes — repo (with project-type detection), account (GitHub user profile), and org (organization profile). Use when creating, updating, or aligning a README to org conventions.
development
Audit README.md files against best practices for repos, accounts, or orgs. Detects missing sections, stale links, inconsistent formatting, and convention violations. Use when reviewing README quality across one or many repos.