requirements-conflict-checker
Skill28 starsChanged 8 months agoMITView on GitHub
In this repository105 other files it gives its agents.
- acceptance-criteria-writerSkill
- ambiguity-hunterSkill
- as-is-process-investigatorSkill
- assumption-extractorSkill
- assumptions-constraints-logSkill
- benefit-hypothesis-writerSkill
- breakout-structure-designerSkill
- business-problem-framingSkill
- business-rule-extractorSkill
- catwoe-root-definitionSkill
- constraint-detectorSkill
- critical-thinking-bias-checkSkill
- definition-of-done-drafterSkill
- deliverable-consistency-checkSkill
- edge-case-elicitorSkill
- evidence-gap-reviewSkill
- functional-vs-nonfunctional-splitterSkill
- interview-designSkill
- moscow-prioritisationSkill
- observation-study-planSkill
- pestle-analysisSkill
- porters-five-forcesSkill
- power-interest-gridSkill
- probe-question-generatorSkill
- problem-statement-refinerSkill
- process-modelling-and-improvementSkill
- process-model-specSkill
- proto-requirements-normalizerSkill
- prototype-elicitationSkill
- pyramid-funnel-diamond-interviewerSkill
- questionnaire-designSkill
- questionnaire-pilot-checkerSkill
- raci-matrixSkill
- raci-rasci-builderSkill
- requirements-elicitationSkill
- requirements-gap-auditorSkill
- requirements-interrogatorSkill
- requirements-packagerSkill
- requirements-prioritizerSkill
- requirements-quality-checkSkill
- requirements-traceability-starterSkill
- see-i-clarifierSkill
- ssm-analysisSkill
- stakeholder-analysisSkill
- stakeholder-communication-plannerSkill
- stakeholder-registerSkill
- strategy-analysisSkill
- swot-prioritisationSkill
- to-be-process-designerSkill
- use-case-specificationSkill
- value-proposition-analysisSkill
- workshop-designSkill
- acceptance-criteria-writerSkill
- ambiguity-hunterSkill
- as-is-process-investigatorSkill
- assumption-extractorSkill
- assumptions-constraints-logSkill
- benefit-hypothesis-writerSkill
- breakout-structure-designerSkill
- business-problem-framingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
Look for logical contradiction, duplicated intent with different wording, NFR tradeoff tension, and scope mismatch.
- Distinctive: line 39
No silent assumption is used to 'resolve' a contradiction.
- Distinctive: line 48
Prefer short, testable statements over long prose.
- Distinctive: line 53
Do not invent stakeholder intent.
- Distinctive: line 54
Do not convert preferences into mandatory requirements without evidence.
- Distinctive: line 55
Do not hide unresolved ambiguity behind polished wording.
- Distinctive: line 56
Do not collapse functional, non-functional, and business rule concerns into one blob.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
requirements-conflict-checker
Purpose
Detect contradictions, tension, or incompatible expectations across requirements, business rules, policies, and constraints.
Trigger this skill when
- Requirements were gathered from multiple people or stages.
- NFRs may compete with each other or with schedule/cost limits.
- A change request could invalidate earlier decisions.
Expected inputs
- requirements set
- business rules
- constraints
- assumptions
Deliverables
- conflict matrix
- severity-ranked issues
- resolution options
Operating procedure
- Compare requirements pairwise where overlap exists.
- Look for logical contradiction, duplicated intent with different wording, NFR tradeoff tension, and scope mismatch.
- Describe the impact of each conflict and the likely owner who must resolve it.
- Suggest resolution paths rather than silently choosing one.
Quality gates
- Conflicts are concrete and source-linked.
- Tradeoffs are explicit.
- No silent assumption is used to 'resolve' a contradiction.
Handoff targets
- requirements-prioritizer
- decision-log if present
- problem-statement-refiner
Output style
- Be explicit about uncertainty.
- Prefer short, testable statements over long prose.
- Surface risk and ambiguity instead of guessing.
- Separate facts, assumptions, constraints, and open questions.
Failure modes to avoid
- Do not invent stakeholder intent.
- Do not convert preferences into mandatory requirements without evidence.
- Do not hide unresolved ambiguity behind polished wording.
- Do not collapse functional, non-functional, and business rule concerns into one blob.
Minimum output skeleton
## Summary
## Findings
## Structured outputs
## Assumptions
## Constraints
## Open questions
## Recommended next skillDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

