confidence-check

name	confidence-check
description	Validate implementation confidence and surface uncertainties before coding. Use when user says "confidence check", "ask for more details", "validate plan", or after task document is created but before implementation. Ensures 95%+ confidence on all items and surfaces change requests.

Confidence Check

Validates implementation readiness by evaluating confidence levels and surfacing uncertainties.

Workflow

Step 1: Review Current Context

Examine all descriptions, plans, and decisions made so far:

• Task document content
• Q&A decisions
• Implementation plan
• File changes planned

Step 2: Confidence Evaluation

For each implementation item, evaluate confidence level:

| Item | Confidence | Gap |
|------|------------|-----|
| Database schema changes | 98% | — |
| Server action authorization | 85% | Unclear role hierarchy |
| UI component props | 90% | Missing loading state spec |

Confidence criteria:

• 95%+ = Ready to implement
• 80-94% = Needs clarification
• <80% = Significant gaps, requires discussion

Step 3: Settled Work Impact Review

Re-evaluate whether implementation would modify settled work:

Only consider modifications if they materially affect correctness, scalability, or safety.

Ignore:

• Elegance improvements
• Stylistic changes
• Speculative future needs

If material impacts found, prepare Change Requests:

⚠️ Change Request #1: [Settled Item]
- Current: [What exists]
- Required change: [What needs to change]
- Why material: [Correctness/Scalability/Safety reason]
- Approval needed before implementation

If no material impacts:

"No change requests required — implementation does not materially impact settled work."

Step 4: Address Gaps

For items below 95% confidence, ask clarifying questions:

**Q[N]: [Topic]**

Current understanding: [What I think is needed]
Uncertainty: [What's unclear]

- **Option A:** [Interpretation 1]
- **Option B:** [Interpretation 2]
- **Option C:** [Interpretation 3]

*My recommendation: Option [X]* - [Rationale]

Step 5: Confidence Summary

Present final assessment:

## Confidence Summary

**Overall: [X]%**

✅ Ready (95%+):
- [Item 1]
- [Item 2]

⚠️ Clarified this session:
- [Item 3] — resolved via Q1
- [Item 4] — resolved via Q2

🔄 Change Requests (require approval):
- CR#1: [Description]

**Status:** [Ready for implementation / Awaiting answers / Awaiting CR approval]

Step 6: Implementation Gate

Only proceed when:

• All items at 95%+ confidence
• All questions answered
• All Change Requests approved (or confirmed none needed)

State clearly:

"Confidence check complete. All items at 95%+ confidence. Ready for implementation."

OR

"Awaiting [answers to Q1-Q3 / approval for CR#1] before implementation can proceed."

Example Usage

User: "confidence check"

Response:

1. Review task document and plans
2. Evaluate: 3 items at 98%, 2 items at 87%
3. Check settled work: No material impacts
4. Ask 2 clarifying questions for low-confidence items
5. After answers: "All items at 95%+. Ready for implementation."

Key Principles

• 95% threshold: Don't proceed with uncertainty
• Material changes only: Don't flag stylistic concerns
• Options format: Questions always have A/B/C with recommendation
• Explicit gate: Clear yes/no on implementation readiness