What problem does it solve? Product materials like PRDs, HTML prototypes, and API contracts are ambiguous and incomplete, so AI-generated implementation tickets often bake in unconfirmed assumptions. This Skill turns those materials into a human-owned specification with evidence-backed gap analysis and tickets that an implementation agent can execute without inventing product semantics. ## Core Features & Use Cases - Specification Convergence: Ingests PRDs, prototypes, contracts, code, and runtime behavior into a Delivery Spec, Interaction Spec, and decision model with stable IDs (REQ, RULE, STATE, SCN, DEC, GAP) and explicit provenance classification. - Human Decision Gates: Enforces Intent, Semantic/Risk, Delivery, and Product Outcome gates, generating ranked Decision Packets instead of vague clarification questions. - Evidence-Backed Gap Analysis: Compares desired behavior against actual code and runtime evidence before creating any ticket, so absence of evidence is never mislabeled as a confirmed gap. - Use Case: Given an HTML prototype and backend API docs for a new feature, run Analysis Mode to produce a validated spec, a gap report with code evidence, and a queue of ready-for-agent tickets; then optionally hand approved tickets to a ticket queue executor for implementation and real Chrome acceptance. ## Quick Start Invoke $spec-to-executable-tickets in Analysis Mode with your PRD, prototype, and API docs to produce validated specifications and dependency-ready tickets.
