cdevadv

A devil's advocate analysis challenges core architectural and strategic assumptions by systematically questioning design decisions across spec, review, test, and implementation layers. This process surfaces hidden flaws and delivers concrete, evidence-based recommendations grounded in repository code and history.

Performing risk analysis on existing architecture involves applying mode-based evaluation using theme, signals, and layers modes. This systematically reviews design, testing, and QA layers to surface risky assumptions and generates safer trade-offs that improve system robustness and alignment with project goals.

Yes, devil's advocate review works for quality assurance and code verification by systematically challenging accepted strategies across QA and verification layers. It uses repository evidence to reveal hidden assumptions and guides teams toward safer, more robust implementation trade-offs.

To start a devil's advocate analysis, state a specific thesis to challenge and select an analysis mode. The Skill conducts multi-pass evaluations across your project layers, providing mandatory progress notes and concrete recommendations grounded in your repository's code and documentation.

Yes, devil's advocate system design review cites repository evidence to ground its insights. It analyzes your code, documentation, and commit history to ensure that architectural risk analysis and actionable recommendations are based on concrete project facts rather than abstract theory.