readiness-gatelisted

Use at every 'are we ready?' moment — before declaring a task done, shipping, demoing, advancing to the next phase, or answering 'so everything works and we're good?'. Replaces vibes-based confidence ('should work now', 'looks good') with an explicit, evidence-backed go/no-go: what was verified and how, what was NOT verified, what changed, and the honest residual risk. Calibrates certainty to evidence — never asserts '100% sure' beyond what was actually tested, and never truncates the findings to fit a tidy summary. Use when reporting completion of any unit of work, when the user asks for a readiness check against a spec or checklist, or when you catch yourself about to say 'this should work'.
mikestangdevs/craft-skills · ★ 2 · Code & Development · score 75

Install: claude install-skill mikestangdevs/craft-skills

# Readiness Gate ## The failure mode this fixes "Done. Should work now." — the most expensive sentence in agent-assisted engineering. The user ships, demos, or builds on top of it, and discovers in production what "should" was hiding. When they come back burned, the trust loss costs more than the bug: now every future "done" gets re-verified by hand, and the agent's leverage collapses. The root defect is uncalibrated confidence. Agents report completion as a mood ("everything looks good!") rather than a claim with evidence. They answer "are you sure?" with escalating enthusiasm instead of escalating proof. And under pressure to be concise, they truncate exactly the part that matters — the caveats, the unverified paths, the one failing edge they decided was probably fine. A readiness gate makes "done" a structured claim: **verified / not verified / changed / residual risk / go or no-go.** It's allowed to say no-go. It's *required* to say what it doesn't know. ## When to Use This Skill - Finishing any unit of work, before reporting it complete - Before a ship, demo, deploy, or handoff — anything with an audience or a blast radius - The user asks "are we ready?", "are you sure?", "so everything works?" - Checking deliverables against a spec, checklist, or requirements doc - You notice the words "should", "probably", or "looks good" forming in a completion report **Don't use when:** mid-task on intermediate steps (gates are for boundaries, not every commit), or for trivial