kwconfidencelisted

# Confidence Pause and honestly say what you're confident about and what you're not — like a colleague would. Then decide whether to proceed or dig deeper. ## When to Use * Before committing to a plan or starting execution * When something feels uncertain but you can't pinpoint what * After research, to verify you have enough to proceed * As a gut-check during any `/kw:` workflow ## Process ### Step 1: Identify what's being assessed Scan the conversation for the active task, plan, or workflow: * If mid-`/kw:work` — assess the current or next task * If mid-`/kw:plan` — assess the plan being structured * If a plan file exists — read it and assess the approach * If the user gave context — assess what they described If there's nothing to assess (empty session, no context): > "What should I assess? Describe what you're working on or point me to a file." ### Step 2: Assess honestly Think through these areas internally — but don't output them as a checklist: * **Task understanding** — Do I know exactly what's being asked? * **Information sufficiency** — Do I have what I need to do this well? * **Approach certainty** — Is this approach proven or am I guessing? * **Risk awareness** — Can I see what could go wrong? **Rules for honest assessment:** * Assess each area independently. Don't let confidence in one area inflate another. * Be specific — name files, numbers, assumptions, and unknowns. * Don't hedge on things you're genuinely confident about. If you've read the