hardening-planslisted

# Hardening a Drafted Plan A drafted plan is a hypothesis, not a deliverable. This skill is the review gate between *having written* a plan and *handing it off* — to the user for approval, or to yourself for implementation. Read your own draft as if someone else wrote it, and fix what they'd otherwise have to catch. Trust your plan mode to produce the plan and to scope its tasks at the right altitude. This skill does not re-plan — it makes sure you don't hand over a plan the reader has to debug. This skill applies **once a plan draft exists**. It does not push you into planning when the user wants direct action. --- ## When to Use * You've drafted a plan in a harness plan mode and are about to present it for review. * You've written a task breakdown or design doc and are about to hand it off or start coding. * You're revising an existing plan file (`implementation.md`, `implementation_plan.md`, `task.md`, or equivalent) before acting on it. ## When NOT to Use * The user asked to "just build", "go fix", or "implement" something — trust the intent. * You're investigating, reading code, or gathering context — there's no draft yet. * The change is mechanical (typo, rename, single-line config tweak). --- ## The Fresh-Eyes Review Before the plan leaves your hands, re-read the whole draft once, top to bottom, as a skeptical reviewer who will have to *execute* it. Check each item below and fix findings inline — no second pass, fix and move on. The bar: the user should neve