conflict-analyzer

Analyze software requirements to detect and resolve eight types of conflicts.

142|14|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/ArabelaTso/Skills-4-SE --skill conflict-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conflict-analyzer
Source: https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/conflict-analyzer
Command: npx skills add https://github.com/ArabelaTso/Skills-4-SE --skill conflict-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill identifies and resolves conflicting requirements that can block development, cause rework, and lead to project delays.

Core Features & Use Cases

  • Conflict Detection: Identifies 8 types of requirement conflicts (logical, technical, resource, temporal, data, state, priority, scope).
  • Impact Assessment: Evaluates the severity and downstream impact of each conflict.
  • Resolution Strategies: Recommends actionable solutions with pros, cons, and effort estimates.
  • Use Case: When reviewing a new set of user stories, use this Skill to automatically flag any contradictions or incompatibilities before development begins, ensuring a smoother implementation.

Quick Start

Use the conflict-analyzer skill to analyze the provided requirements document for any conflicts.

Frequently Asked Questions about conflict-analyzer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect conflicting requirements in a software engineering project?

Conflict detection involves analyzing requirements across logical, technical, resource, temporal, data, state, priority, and scope dimensions to identify contradictions that can block development and cause project delays.

What types of requirement conflicts should I look for during analysis?

During requirement analysis, you should look for 8 types of conflicts: logical, technical, resource, temporal, data, state, priority, and scope conflicts that cause incompatibilities within user stories.

How do I perform impact assessments for requirement conflicts?

Impact assessment for requirement conflicts evaluates the severity and downstream impact of each identified conflict to determine its potential to cause development rework and project delays.

What is the best way to resolve requirement conflicts in user stories?

The best way to resolve requirement conflicts is to generate actionable resolution strategies that include dependency mapping, pros, cons, and effort estimates for each identified incompatibility.

Can I use automated conflict detection for project management reviews?

You can use automated conflict detection during project management reviews to automatically flag contradictions or incompatibilities in new sets of user stories before implementation starts.

When do I need requirement conflict analysis to prevent rework?

You need requirement conflict analysis when reviewing a new set of user stories to automatically flag contradictions or incompatibilities early, ensuring smoother implementation and preventing development rework.