honest-reflections

# Honest Reflections Skill

## Overview

**Purpose**: Systematic gap analysis using 100+ sequential thoughts to identify discrepancies between claimed completion and actual delivery. Prevents premature completion declarations by revealing assumptions, partial work, missing components, and rationalization patterns.

**Core Value**: Catches the moment when you're about to claim "100% complete" on 50% completion.

**Key Innovation**: Self-assessment protocol that replicates critical external review, catching gaps before they become credibility issues.

---

## When to Use This Skill

### MANDATORY (Must Use)

Use this skill when:
- **Before declaring work "complete"**: Any statement like "all done", "100% finished", "scope complete"
- **Final commit before handoff**: Last commit of major work session
- **Completion milestones**: MVP complete, phase complete, project done
- **Quality gate reviews**: Before presenting work to stakeholders
- **After long work sessions**: 6+ hours of continuous work without checkpoint

### RECOMMENDED (Should Use)

- After each major phase of multi-phase project
- When tempted to rationalize skipping remaining work
- Before creating handoff documentation
- When user asks "is it really complete?"
- Periodic self-audits (weekly for long projects)

### CONDITIONAL (May Use)

- Mid-project health checks
- When feeling uncertainty about completeness
- After receiving feedback suggesting gaps
- Learning from past incomplete deliveries

### DO NOT Rationalize Skipping Because

❌ "Work looks complete" → Appearances deceive, systematic check required
❌ "I'm confident it's done" → Confidence without verification is overconfidence
❌ "Takes too long" → 30-minute reflection prevents hours of rework
❌ "Already did self-review" → Mental review misses 40-60% of gaps
❌ "User didn't explicitly ask" → Professional responsibility to verify completion

---

## Anti-Rationalization (From Baseline Testing)

**CRITICAL**: Agents systematically skip honest reflect