confidence-check

# Confidence Check — earn the right to start <!-- routing-eval reads this line; it lives in the BODY so the always-on skill LISTING stays inside Claude Code's budget (1% of the context window) — an overflowing listing gets descriptions truncated or dropped, which strips the very keywords a match depends on. --> Trigger phrases: "confidence check", "ready to implement", "before I start", "am I sure enough", "readiness" ## When Right before implementation code gets written for anything beyond a one-line change, and *after* the scope is clear ([[spec-planning]] / planner). Every other gate in this kit fires at the end — review, DoD, the commit approval. Those catch bad code. None of them catch **good code that should never have been written**: the duplicate of a helper that already exists, the pattern that fights the project's architecture, the call built against an API that behaves differently than remembered. That waste is invisible to a reviewer, because what they see is a clean diff. ## The five checks Each is answered with **evidence**, not with a feeling. Name what you ran or read. | # | Check | How it is actually answered | |---|---|---| | 1 | **Does it already exist?** | Grep/Glob the codebase for the behaviour *and* its likely other names. A near-duplicate counts. | | 2 | **Does it fit this project?** | Read `CLAUDE.md` + the relevant project skill. Same stack, same pattern, no new dependency smuggled in. | | 3 | **Is the external claim verified?** | The A...