TheGoat395/Codex-Skills / skills/final-client-handoff
final-client-handoff
VerifiedPrepare verified ownership and delivery notes.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.9 KB |
| agents/openai.yaml | config | 268 B |
| references/evidence-record-schema.md | markdown | 2.9 KB |
| references/final-client-handoff-guide.md | markdown | 1.9 KB |
| references/release-handoff-template.md | markdown | 737 B |
| scripts/verify-handoff.py | script | 6.7 KB |
SKILL.md
View on GitHub---
name: final-client-handoff
description: "Prepare verified ownership and delivery notes."
---
# Final Client Handoff
Use this skill to give the user a calm, accurate closeout they can trust and act on.
## Closeout modes
For a small change, report changed files, actual checks and remaining limits; no release manifest is required. For a client release, aggregate existing applicable ownership, tested/untested, recovery and release evidence using the full procedure below.
## Workflow
1. Inspect the affected surface, relevant project scripts, target URL and available inspection tooling; reuse existing context.
2. Read [Final Client Handoff Guide](references/final-client-handoff-guide.md) before claiming the site is ready.
3. Run the narrowest meaningful checks for the risk: visual, mobile, accessibility, performance, forms, media, SEO, analytics, deployment, or handoff.
4. Fix issues when they are in scope; otherwise record exact evidence and remaining risk.
5. Summarize commands, URLs, screenshots/checks, changed files, and what was not tested.
For a full client release, use [references/release-handoff-template.md](references/release-handoff-template.md) for the release, monitoring, recovery, and ownership record. Validate it with `python3 "<skill-root>/scripts/verify-handoff.py" <handoff.json>`.
## Scoped execution
Apply the [shared web contract](../website-operating-rules/references/scoped-web-contract.md) once when execution crosses phases; reuse it if already read. Load only the specialist guidance relevant to the requested surface and deliverable.
For helper-driven evidence, use the [typed record schema](references/evidence-record-schema.md). The helper validates structure only; use actual inspection/test results for claims.
Resolve `<skill-root>` to this skill folder's actual absolute location; preserve project-local module resolution for Node capture tools.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |