What problem does it solve? Turning a well-specified ticket into working code often fails because tickets encode assumptions about the codebase that may be wrong, plans get lost when sessions end, and acceptance criteria go unverified. This Skill implements a single ticket end to end: it verifies the ticket's assumptions against the real repository, gets an implementation plan approved, writes the code with @spec traceability annotations, and keeps a delivery record current from plan approval onward. ## Core Features & Use Cases - Pre-Flight Reconciliation: Verifies every assumption a ticket depends on (schema objects, scripts, pinned documents, predecessor outputs) against the actual repository before planning, blocking the delivery if a required foundation is missing. - Checkpointed Delivery Record: Writes the record progressively (Reconciled → In Progress → Delivered) so a compacted or resumed session continues from the approved plan without re-asking for approval. - Verified Acceptance Criteria: Executes tests, type-checks, lints, and builds with recorded commands and exit codes; a criterion with no executed evidence is marked Unverified, never ticked. - Use Case: After ticket breakdown produces TICKET-004 for a search capability area and its dependencies are delivered, run the delivery skill to reconcile the ticket against the schema, present an implementation plan for approval, write the annotated code and tests, and commit the code together with the delivery record. ## Quick Start Ask the AI to implement TICKET-004 in the current change, approving the implementation plan it presents before any code is written.
