conflict-detection

To detect conflicts between project requirements and plans, provide descriptions of current workflow items for analysis. The skill surfaces contradictions during DISCUSS and PLAN phases to identify conflicting requirements, decisions, and plans early.

The best way to resolve workflow conflicts is to analyze the conflicting items and document the resolution rationale. This skill enforces early detection, halts progression on conflicts, and records rationale to support auditable decision trails.

You document rationale for non-auto-resolution by tracking conflicts with clear escalation options and recording the reasoning. This ensures structured conflict tracking and supports auditable decision trails for future traceability.

Yes, you can use conflict detection for product development workflows. It applies specifically during the DISCUSS and PLAN phases to mitigate conflicts between requirements, decisions, and plans across the project lifecycle.

Workflow progression halts when conflicts are detected to enforce early detection and prevent moving forward with contradictions. This ensures issues are managed transparently and resolution rationale is documented before proceeding.