What problem does it solve? At a handoff between roles (e.g., PO to Tech Lead), it is unclear whether a PRD, SRS, or other phase document is complete enough to support the next phase. This Skill reports readiness without generating any output, naming every missing or unclear item by file, section, and the role that owns it. ## Core Features & Use Cases - Readiness gating: Runs the framework's input-check protocol against any phase (intake, prd, srs, techdocs, code, testcases, unit, acceptance, review) and reports READY or NOT_READY. - Role-grouped gap reporting: Groups blocking gaps by owning role (PO/BA, Tech Lead) so the reader immediately knows whether to fix it or hand it back. - Persistent gap recording: Appends blocking gaps to the source document's open-questions table and findings.tsv so the answer survives the terminal session. - Use Case: A Tech Lead picking up a PO's PRD runs /check srs PTK-001 and gets a one-screen verdict listing the two blocking gaps owned by the PO, without generating any SRS content. ## Quick Start Run /check srs PTK-001 to verify whether the PRD for feature PTK-001 is complete enough to begin writing the SRS.