confidence-check

A confidence check validates implementation readiness by enforcing a 30-point self-assessment scoring framework across understanding, context, and approach, requiring concrete evidence for any dimension scored 8 or higher.

A pre-implementation risk assessment checklist scores understanding, context, and approach from 0-10 to identify gaps. It mandates external validation and gap-filling before proceeding with major refactors or feature work.

To stop proceeding with wrong assumptions during feature development, use an anti-gaming protocol that requires concrete evidence for any self-assessment dimension scored 8 or higher before you write code.

You need a confidence check before coding a major refactor when requirements are unclear or you lack sufficient context. It guides escalation and external validation to prevent wasted effort from wrong assumptions.

The best way to score implementation risks before writing code is applying a 30-point scoring framework across understanding, context, and approach, which enforces gap-filling when confidence is insufficient.

When pre-implementation confidence scores are low, follow the checklist guidance for gap-filling and escalation. You must seek external validation to clarify requirements and mitigate risks before proceeding.