Software delivery integrity, as Claude Code skills.

One pre-ship pass over your project's release gates. It works out which gates this launch actually requires, checks them read-only, helps you close the gaps, and leaves the verdict to one independent audit.

Audits the whole application across the dimensions your product implies, from a standing set of eleven. It ends in one scope-qualified decision: safe to ship; ready to ship, risks noted; or do not ship.

You declare a one-page product frame plus a four-line security frame, and the skill audits them like code. Who it is for. What it fixes. What success looks like. What would prove the idea wrong. Blanks are findings.

Declares what the project is (experiment, internal tool, web product, service, or library), then starts it in the shape that kind of project actually needs.

Keeps the docs true to the code and current across every surface: repair the doc, flag a suspected regression, and reconcile the deck, hub, and showcase copy to what shipped.

Pressure-tests a surface the way users actually hold it. It diagnoses the real cause first, then verifies across widths, keyboard, zoom, and real devices.

Names the funnel before the feature, keys every event on the right entity in one identity model, and measures activation instead of vanity.

Writes the next unit's plan while context is hot and indexes it, so the next session resumes from a real handoff instead of a cold guess.

Enforces one voice from a single source of truth across every user-facing word, and never above clarity.