constraint-evaluator

Identify the binding constraint by combining internal project state with external research to score 19 constraints on a 0-5 scale, surfacing the specific bottleneck most limiting progress for objective prioritization.

Theory of constraints risk analysis diagnoses the single factor limiting project throughput. You need it when charters stall and governance decisions require objective evidence to prioritize actions across concurrent phases.

Score constraints by reading ROADMAP.md and related charter files, conducting external searches, then updating work/charters/CONSTRAINTS.md with evidence, 0-5 scores, and rationales to maintain an accurate constraints dashboard.

Yes, you can synthesize independent external research with internal project charters to objectively prioritize bottlenecks, ensuring strategy reviews focus on the binding constraint rather than assumed issues.

The best way to evaluate unchecked phases is combining internal state files with external research to score limitations, updating the constraints dashboard to guide prioritization and governance decisions.

Constraint evaluation requires both because internal charters provide current project state while external searches validate scoring against broader risk-analysis data, ensuring the diagnosis of the binding constraint is objective.