// Pre-implementation confidence assessment (≥90% required). Use before starting any implementation to verify readiness with duplicate check, architecture compliance, official docs verification, OSS references, and root cause identification.
Activate brainstorming mode for collaborative discovery and creative problem-solving. Use when users have vague requests, want to explore ideas, or need requirements discovery.
Activate deep research mode for systematic investigation. Use when the user asks to research, investigate, explore, or needs current information with citations.
Project management with PDCA cycles, confidence checks, and context persistence. Auto-activates at session start to restore context. Use for task planning, progress tracking, and structured development.
Activate ultra-compressed output mode for maximum token efficiency. Use when context is running low, user requests brevity, or dealing with large-scale operations.
Systematic troubleshooting with root cause analysis. Use when users report errors, bugs, or unexpected behavior. Never retry without understanding why.
Pre-implementation confidence assessment (≥90% required). Use before starting any implementation to verify readiness with duplicate check, architecture compliance, official docs verification, OSS references, and root cause identification.
| name | Confidence Check |
| description | Pre-implementation confidence assessment (≥90% required). Use before starting any implementation to verify readiness with duplicate check, architecture compliance, official docs verification, OSS references, and root cause identification. |
Prevents wrong-direction execution by assessing confidence BEFORE starting implementation.
Requirement: ≥90% confidence to proceed with implementation.
Test Results (2025-10-21):
Use this skill BEFORE implementing any task to ensure:
Calculate confidence score (0.0 - 1.0) based on 5 checks:
Check: Search codebase for existing functionality
# Use Grep to search for similar functions
# Use Glob to find related modules
✅ Pass if no duplicates found ❌ Fail if similar implementation exists
Check: Verify tech stack alignment
CLAUDE.md, PLANNING.md✅ Pass if uses existing tech stack (e.g., Supabase, UV, pytest) ❌ Fail if introduces new dependencies unnecessarily
Check: Review official docs before implementation
✅ Pass if official docs reviewed ❌ Fail if relying on assumptions
Check: Find proven implementations
✅ Pass if OSS reference found ❌ Fail if no working examples
Check: Understand the actual problem
✅ Pass if root cause clear ❌ Fail if symptoms unclear
Total = Check1 (25%) + Check2 (25%) + Check3 (20%) + Check4 (15%) + Check5 (15%)
If Total >= 0.90: ✅ Proceed with implementation
If Total >= 0.70: ⚠️ Present alternatives, ask questions
If Total < 0.70: ❌ STOP - Request more context
📋 Confidence Checks:
✅ No duplicate implementations found
✅ Uses existing tech stack
✅ Official documentation verified
✅ Working OSS implementation found
✅ Root cause identified
📊 Confidence: 1.00 (100%)
✅ High confidence - Proceeding to implementation
The TypeScript implementation is available in confidence.ts for reference, containing:
confidenceCheck(context) - Main assessment functionToken Savings: Spend 100-200 tokens on confidence check to save 5,000-50,000 tokens on wrong-direction work.
Success Rate: 100% precision and recall in production testing.