deliver-and-verify
Use when secret scanners refuse, provisioning previews, changing source checkouts, changing SQL queries or fixtures, changing admission or access rules, changing database privileges, changing selected-source release inputs, publishing, editing or arming PRs, changing CI workflows or concurrency, selecting delivery subsets, enrolling disabled tests in CI, running builds or tests in a lease, generating source, upgrading engine or SDK dependencies, benchmarking engines, repairing recovery references or reconcilers, rotating secrets consumed by Jobs, changing resource sizing or retention, changing diagnostic redaction, changing credential input/output guards, implementing or shipping a feature, bug fix, parser, export format, endpoint, checkout or voucher channel, synthetic probe, zero-token external inbox/queue watcher, or authorized operational, repository, marketing, or commercial change. Use challenge for a plan or architecture, prove-it for a review or evidence check, clear-writing fo
Target: Databases. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Deliver and verify
- Step 0: Route the acceptance cases
- Coordinate the work
- Establish the acceptance cases
- Execute and verify
- Domain references
Carry the authorized outcome through execution and verification at the user, partner, or operator surface. Use the existing grants and release path; preserve user data and authorized spending limits. When changing a game, app or SaaS user journey, remaking a product, or publishing assets or configuration that change the experience, or comparing engines, read parity.md before defining the acceptance cases. It owns the screen-and-feature comparison, engine benchmarks, live evidence and automated release checks. For engine or SDK changes affecting controls, account entry or host lifecycle, including restored integrations, read shipping-host verification. Native tests and browser previews can exercise different input and feature paths. For credential import, guest restoration or account-continuity changes, read guest continuity before defining tests; decoding a retained value is not proof that its production consumer keeps it. Shared implementations follow the three architectural invariants: neutral mechanisms with caller-configured policy, zero domain leakage in code/prompts/verifiers/fixtures, and exact causal state/data/authorization guards that fail closed on unreadable required st
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- SylphxAI/skills
- Source file
- skills/deliver-and-verify/SKILL.md
- Fixed revision
- e61c6f49e7bc2ac4f764590438fe01a689addefb
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: SylphxAI/skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T01:01:23.960Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.