Confidence Check Skill

Communication with user: User's language. Documents: English.

Purpose

Validate readiness before major SDD phases. Prevents 5-50K tokens of wrong-direction work by spending 100-200 tokens on verification.

ROI: 25-250x token savings

When to Use

• Before writing spec.md (idea validation)
• Before writing design.md (requirements clarity)
• Before creating tasks (design completeness)
• Before executing tasks (implementation readiness)

Confidence Thresholds

Phase-Specific Checklists

Pre-Spec Confidence (Idea → Spec)

Evidence required:

• Pain point quotes from Reddit/forums/interviews
• Competitor analysis showing gaps
• User persona with real data

Pre-Design Confidence (Spec → Design)

Evidence required:

• Spec.md with all sections complete
• No TBD or unclear items
• User has approved spec

Pre-Task Confidence (Design → Tasks)

Evidence required:

• Design.md approved
• Implementation-plan.md complete
• No TBD in technical decisions

Pre-Implementation Confidence (Task → Code)

Evidence required:

• Task file read and understood
• Related code explored
• No open questions

Workflow

1. Identify phase (spec/design/task/impl)
     ↓
2. Run phase-specific checklist
     ↓
3. Calculate confidence score
     ↓
4. Present results with evidence
     ↓
5. Decision:
   - ≥90%: "Proceed"
   - 70-89%: "Clarify these gaps first"
   - <70%: "Stop - answer these questions"

Output Format

## Confidence Check: {phase}

### Score: {X}% {emoji}

| Check | Status | Evidence |
|-------|--------|----------|
| {check1} | ✅/⚠️/❌ | {evidence or gap} |
| {check2} | ✅/⚠️/❌ | {evidence or gap} |
...

### Verdict: {Proceed / Clarify / Stop}

{If not proceed:}
### Questions to Answer First
1. {question1}
2. {question2}

### Recommended Actions
- {action1}
- {action2}

Integration Points

Call before:

• /spec → pre-spec check
• /design → pre-design check
• faion-make-tasks → pre-task check
• /faion-execute-task → pre-impl check

Anti-Patterns to Catch