Confidence Check

Pre-implementation confidence assessment evaluates five critical areas: duplicate detection, architecture alignment, documentation review, open-source references, and root-cause clarity. This validation produces a 0-1.0 confidence score to confirm readiness, identify gaps, or flag stop conditions before development begins.

Verify that your task hasn't already been implemented, aligns with your system architecture, is documented in official sources, has no existing open-source solutions, and addresses the underlying problem—not just symptoms. These checks reduce costly rework and wasted development effort.

Yes. Confidence checks apply to new features, bug fixes, refactoring, and integration tasks. The same five-point validation—duplicates, architecture, documentation, OSS references, and root-cause clarity—ensures all development work rests on solid assumptions before implementation.

The confidence score (0-1.0) synthesizes weighted checks across duplicates (25%), architecture (25%), documentation (20%), open-source references (15%), and root-cause clarity (15%). Scores indicate readiness to proceed, areas requiring investigation, or conditions to stop and reassess.

A low score signals missing validation in one or more areas—unresolved duplicates, architectural misalignment, insufficient documentation review, overlooked OSS solutions, or unclear root causes. The assessment identifies which gaps to close before coding begins.