conflict-analyzer
Identifies and analyzes conflicts in software requirements including logical contradictions, technical incompatibilities, resource constraints, timeline issues, data conflicts, and stakeholder priority mismatches. Use when reviewing requirement sets, specifications, user stories, or project plans to detect conflicts that could block implementation or cause rework. Provides detailed conflict analysis with resolution strategies and impact assessment.
npx skills add majiayu000/claude-skill-registry --skill conflict-analyzer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Requirement Conflict Analysis You are an expert requirements analyst who identifies and resolves conflicts between software requirements. ## Core Capabilities This skill enables you to: 1. **Detect conflicts** - Identify 8 types of requirement conflicts 2. **Assess impact** - Evaluate technical, business, and timeline consequences 3. **Analyze dependencies** - Map requirement relationships and conflict chains 4. **Recommend resolutions** - Suggest appropriate resolution strategies 5. **Generate reports** - Create structured conflict analysis with actionable recommendations ## Analysis Workflow Follow this process when analyzing requirements for conflicts: ### Step 1: Catalog All Requirements Collect and organize all requirements: - Extract from documents, user stories, tickets - Assign unique IDs if not already present - Group by feature, component, or domain - Note stakeholder sources - Identify dependencies between requirements ### Step 2: Systematic Conflict Detection Use `references/conflict_patterns.md` to scan for 8 conflict types: **1. Logical Conflicts** - Direct contradictions (A says yes, B says no) - Mutually exclusive features - Opposite behaviors - Example: "Work off
- Core Capabilities
- Analysis Workflow
- Step 1: Catalog All Requirements
- Step 2: Systematic Conflict Detection
- Step 3: Build Conflict Matrix
- Step 4: Assess Conflict Severity
- Step 5: Analyze Dependencies
- Step 6: Recommend Resolution Strategies
- Step 7: Create Conflict Report
- Output Formats
- Best Practices
- Common Pitfalls to Avoid
- Example Analysis
- Resources
What does the conflict-analyzer skill do?
Identifies and analyzes conflicts in software requirements including logical contradictions, technical incompatibilities, resource constraints, timeline issues, data conflicts, and stakeholder priority mismatches. Use when reviewing requirement sets, specifications, user stories, or project plans to detect conflicts that could block implementation or cause rework. Provides detailed conflict analysis with resolution strategies and impact assessment.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill conflict-analyzer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.