agentleFS
45ck45ck/business-analysis-skills/.agents/skills/requirements-conflict-checker/SKILL.md

requirements-conflict-checker

Skill28 starsChanged 8 months agoMITView on GitHub

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
  1. Distinctive:

    Look for logical contradiction, duplicated intent with different wording, NFR tradeoff tension, and scope mismatch.

    line 32
  2. Distinctive:

    No silent assumption is used to 'resolve' a contradiction.

    line 39
  3. Distinctive:

    Prefer short, testable statements over long prose.

    line 48
  4. Distinctive:

    Do not invent stakeholder intent.

    line 53
  5. Distinctive:

    Do not convert preferences into mandatory requirements without evidence.

    line 54
  6. Distinctive:

    Do not hide unresolved ambiguity behind polished wording.

    line 55
  7. Distinctive:

    Do not collapse functional, non-functional, and business rule concerns into one blob.

    line 56

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Compare requirements pairwise where overlap exists.
  2. Look for logical contradiction, duplicated intent with different wording, NFR tradeoff tension, and scope mismatch.
  3. Describe the impact of each conflict and the likely owner who must resolve it.
  4. 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 skill

Download now (ZIP)

Does 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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.