Requirement prioritization is an inherently important step in the DevOps framework. Unfortunately, the prioritization process often disregards the non-functional requirements and the possible conflicts among them. This implies that unresolved dependencies and conflicts would be identified at integration time only, which may lead to major refactoring issues. We introduce CARO a new tool that generates an ordering among the requirements based on conflicts and dependencies among the requirements. The tool provides a quantitative risk evaluation framework along with risk mitigation strategies based on conflicts and dependencies among the requirements.