What problem does it solve? Feature work often ships with only spot-checked validation, leaving Success Criteria and Functional Requirements unverified or silently assumed to pass. This Skill closes that gap by running a feature's quickstart or acceptance checklist as a strict integration gate where every requirement must be bound to an executed step. ## Core Features & Use Cases - Full Coverage Mapping: Binds every Success Criterion and Functional Requirement in the spec to a concrete, executed checklist step, flagging unbound items as explicit GAPs. - Three-State Verdicts: Marks each row pass, fail, GAP, or blocked, so missing environments or dependencies never masquerade as coverage. - Bidirectional Traceability: Confirms every checklist step maps back to a named requirement, flagging orphan checks that validate nothing. - Use Case: After implementing a feature with a quickstart guide, run this gate to produce a coverage ledger proving each spec claim was actually executed — including reinstall-survival scenarios — before declaring the feature done. ## Quick Start Run the quickstart checklist for this feature as an integration gate and produce a coverage ledger mapping every Success Criterion and Functional Requirement to executed steps.
