Protocol Conflict Analysis
Independent PiSkill directory guide. The original prompt remains hosted by Microsoft PromptKit.
What does this prompt do?
Compares protocol requirements, implementations, and dependent artifacts to locate incompatible assumptions, ordering rules, states, messages, or version expectations.
Primary use case
Analyze conflicting requirements across a software protocol.
Expected output
Traceable protocol conflicts and required decisions.
Inputs or variables
- protocol specifications
- implementation evidence
- version context
Related prompts
Infrastructure Review
Reviews infrastructure definitions and deployment topology for correctness, security, resilience, maintainability, cost risks, and consistency with operational requirements.
Integration Compliance Audit
Reviews an integration against interface, configuration, security, lifecycle, error, and operational requirements, separating proven compliance from missing evidence.
Interface Contract Audit
Checks APIs or component boundaries against a declared interface contract, including inputs, outputs, errors, compatibility, and behavioral invariants.
Library Consistency Audit
Checks a reusable library for inconsistent APIs, naming, errors, configuration, documentation, tests, and behavioral patterns that make adoption harder.
Specification Alignment Audit
Cross-checks related specifications and implementation artifacts for conflicting requirements, terminology drift, missing traceability, and incompatible assumptions.
Code Compliance Audit
Audits implementation code against explicit engineering requirements and reports supported compliance gaps without substituting preferences for documented rules.