analyzing-contradictions

A go-to-market review phase that looks across earlier research and strategy documents for contradictions, missing assumptions, and unresolved objections. Go-to-market means the plan for reaching customers and selling a product.

In plain words
What is it for?
Checking a product's capability profile, competitor research, market analysis, product-market-fit assessment, and sales strategy before finalizing the go-to-market plan.
Why use it?
It can expose conflicts such as a sales plan depending on capabilities the product does not have, or market assumptions that do not fit the product assessment.

Skill for Claude CodeCodex

Part of the market-research plugin — 8 skills shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/qte77/claude-code-plugins/analyzing-contradictions
Any agent
npx skills add qte77/claude-code-plugins --skill analyzing-contradictions
Clone the repo
git clone --depth 1 https://github.com/qte77/claude-code-plugins

Made for: Claude Code, Codex.

Or install market-research, the plugin that ships this one along with the rest of its 8 skills.

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 797 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00048 $0.00797
Opus 5 $0.00024 $0.00398
Sonnet 5 $0.00010 $0.00159
Haiku 4.5 $0.00005 $0.00080

Measured 2d ago against content hash 7605d16e1ff8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

analyzing-contradictions scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/market-research/skills/analyzing-contradictions/SKILL.md · 94 lines

How it starts

The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Analyzing Contradictions (Phase 4)

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.

Mode Awareness

Read config/mode.md before starting:

  • concise — Top 3 contradictions + top 5 objections (brief)
  • detailed — Full contradiction register, root cause analysis, resolution roadmap
  • conservative — Surface all contradictions regardless of severity; prefer resolution over ignoring
  • ambitious — Frame contradictions as opportunities; propose bold resolutions

Inputs

  • results/phase-0/capability-profile.md
  • results/phase-1a/competitor-map.md
  • results/phase-1b/market-analysis.md
  • results/phase-2/pmf-assessment.md
  • results/phase-3/gtm-strategy.md
  • config/mode.md — Style and approach settings

Contradiction Detection Areas

  • Phase 0 vs Phase 3: Does the GTM strategy require capabilities the product lacks?
  • Phase 1A vs Phase 3: Does the channel strategy ignore how competitors already dominate those channels?
  • Phase 1B vs Phase 2: Does the PMF score contradict market sizing assumptions?
  • Phase 2 vs Phase 3: Does the segment prioritization conflict with PMF evidence?
  • Internal Phase 3: Are ICP definitions consistent with channel strategy?

Workflow

  1. Read all prior phase outputs systematically
  2. Identify cross-phase tensions — Claims or recommendations that conflict
  3. Identify intra-phase gaps — Missing evidence, unsupported assumptions
  4. Draft objection list — What will skeptical investors or buyers say?
  5. Propose resolutions — How should each contradiction be addressed?
  6. Validate against criteria — Check config/validation_criteria.md Phase 4 gates

Output

Write 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]

Read the full file on GitHub · 94 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 94 lines · 48 tokens per session scan A 7605d16e1ff8

Subscribe to this mod's changes

analyzing-contradictions is a skill published in the GitHub repository qte77/claude-code-plugins (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 48 tokens to every session and 797 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

orchestrator

FULLY AUTONOMOUS Flutter development pipeline orchestrator. Smart routing: PM analyzes -> creates targeted tasks -> Orchestrator executes only needed agents. Supports Asana task URLs. Includes QE verification via Maestro E2E tests. 7-phase flow: PM -> TodoWrite -> Execute -> Review -> Tests -> QE E2E -> Close.

aleksandr-chaika/flutter-clean-arch-skills · 72 tokens

flutter-guide

Flutter/BLoC Clean Architecture patterns, review checklists, and testing guides. Background knowledge for flutter-dev, flutter-reviewer, flutter-tester. Not user-invocable.

aleksandr-chaika/flutter-clean-arch-skills · 39 tokens

maestro-flutter

Maestro E2E testing knowledge for Flutter apps. YAML-based flows, TestKeys, visual regression, Maestro MCP integration. Background knowledge for QE E2E testing phase.

aleksandr-chaika/flutter-clean-arch-skills · 41 tokens

android-kotlin-compose

Android development with Kotlin and Jetpack Compose. Use when user mentions "Compose", "Jetpack Compose", "Material3", "Hilt", "Room", "ViewModel", or needs to build Android UI, implement MVVM architecture, manage Compose state, or integrate Jetpack libraries (Navigation, Room, Hilt, ViewModel). Triggers on…

and3r817/dot-claude-plugins · 84 tokens

android-kotlin-coroutines

Android development with Kotlin Coroutines and Flow. Use when user mentions "coroutines", "suspend", "Flow", "StateFlow", "SharedFlow", "viewModelScope", "lifecycleScope", or needs to implement async programming, handle structured concurrency, integrate coroutines with Retrofit/Room/WorkManager, or write coroutine…

and3r817/dot-claude-plugins · 87 tokens

codex-advisor

Advisory consultation skill for architectural reviews, design decisions, code analysis, and technology evaluation. Codex provides recommendations without making code changes. Invoked by phrases like "consult Codex", "get Codex's opinion", "ask Codex about", "have Codex review", "Codex analysis", "validate this…

and3r817/dot-claude-plugins · 85 tokens