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 |
references/final-client-handoff-guide.md
View on GitHub# Final Client Handoff Guide
## Purpose
- Give the user a calm, accurate closeout they can trust and act on.
## Discovery Questions
- What changed?
- What commands and browser checks actually ran?
- Where can the user view the result?
- What is not tested or still risky?
- What next steps are genuinely useful?
## Implementation Rules
- Keep handoff concise and evidence-based.
- Do not hide failed commands or skipped tests.
- Include URLs and file links when useful.
- Mention env vars without secret values.
- Avoid ending with vague optional fluff.
## Useful Patterns
- Changed files, commands run, local/deployed URL, verification, not tested, next risk.
- Design summary plus QA summary.
- Deployment handoff with production URL and smoke checks.
- CMS/env handoff with safe variable names and editor notes.
## Anti-Patterns
- All done, no details.
- Claims browser QA ran when it did not.
- Secret values in summary.
- Ten speculative next steps.
## QA Checklist
- Cross-check final answer against tool outputs.
- Confirm no running sessions are needed.
- Report failed/skipped checks.
- Use concise file links.
## Acceptance Criteria
- The user knows what changed and how it was verified.
- Risks are honest.
- The handoff is short enough to be useful.
## 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.
## Official Source Anchors
- Playwright screenshots: https://playwright.dev/docs/screenshots
- Playwright visual comparisons: https://playwright.dev/docs/test-snapshots
- Playwright emulation: https://playwright.dev/docs/emulation
- Vercel deployments: https://vercel.com/docs/deployments
- Vercel environment variables: https://vercel.com/docs/environment-variables
- GitHub Pages: https://docs.github.com/en/pages
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 |