What problem does it solve? Before handing a night to an unattended autonomous coding run, you need to know the project is defined well enough to survive without you. This Skill acts as a boot gate: it reads the project's own definition artifacts and refuses to green-light a run that would stall on missing objectives, undeclared runtime surfaces, or an unbounded governor envelope. ## Core Features & Use Cases - Per-criterion readiness ledger: Reads PROJECT_CHARTER.md, SOURCE_OF_TRUTH.md, DECISIONS.md, and IMPLEMENTATION_PLAN.md through a shared definition-completeness reader and emits a RUN_READINESS.md ledger with present/partial/missing status per criterion. - BOOT or NOT-READY verdict: Returns NOT-READY naming every concrete gap, including declared runtime surfaces (web, backend HTTP, mobile, game, database) that have no evidence adapter to produce morning artifacts. - Report-only gate: Never answers a criterion on the operator's behalf, never edits decisions or plans, and never substitutes for plan approval. - Use Case: Before launching an overnight autonomous-run on a web app task, run this gate to confirm the charter, locked decisions, declared surfaces, and wall-clock governor limits are all in place; if the database surface lacks an adapter, you get NOT-READY naming that exact gap instead of a wasted night. ## Quick Start Check whether my current task is ready for an unattended overnight autonomous run and list any missing definition gaps.
