claude/skills/client-handover/SKILL.md at 9da5d8d52c85a5e738f168075861dc1d7e818ccc

Files

T

Bastien Chanot 07253e093c feat(doctrine): W6 — prose sweep + BDR-077 + LRN-137 + plan execution notes

LRN-113 whole-surface sweep: client-handover x2 + commit-change prose
repointed to the two-mode reality; code-cleaner/status historic notes
kept (accurate). Memory: BDR-077 (full architecture), LRN-137
(mode-based re-tiering + fail-safe pin rule), journal. Plan carries
as-built EXECUTION NOTES.

2026-07-19 23:44:24 +02:00

5.2 KiB

Raw Blame History

name, description, argument-hint, allowed-tools

name

description

argument-hint

allowed-tools

client-handover

Use when finalizing a project for non-technical client delivery — final audits, live-site validation, branded deliverable (MD + HTML + PDF). Orchestrator: client-handover-writer spawns /seo + /harden in parallel, then /web-validate, then writes the deliverable. Triggers: "client handover", "livraison client", "rapport client", "deliverable", "livrable", "finaliser et livrer".

optional
language fr\|en

--include-deploy

--skip-deploy

--skip-seo

--skip-audits

--skip-fix-loop

--max-iterations N

--audit-max-age <duration>

--output <path>

Read

Write

Edit

Bash

Grep

Glob

WebSearch

WebFetch

AskUserQuestion

Agent

MODEL GATE (blocking): run $HOME/.claude/lib/model-gate.md BEFORE loading the agent below. Verdict small → STOP — print the gate's remedy, end the turn, do not load the agent.

Load and follow strictly:

$HOME/.claude/agents/client-handover-writer.md

Execute the CLIENT HANDOVER WRITER agent on this project. It runs the audit/fix/gate pipeline INLINE on the big session model (gated above), its skill-runner children dispatched model: "fable", then delegates the client deliverable to the two-mode handover-doc-writer subagent — synthesize on opus, render (Markdown + branded HTML + PDF) on the sonnet pin (BDR-077).

The agent runs a ship-and-handover pipeline with explicit gates:

PRE-FLIGHT — Detect git repo, project root, language, project type, web sub-type, NAP signals, stack.
BASELINE AUDITS — Run /seo (SEO+GEO) and /harden in parallel. Capture initial scores (SCORE_SEO_BEFORE, SCORE_GEO_BEFORE, SCORE_HARDEN_BEFORE).
FIX LOOPS (parallel, bounded) — For each audit < 17/20:
- Re-invoke the audit subagent with explicit instruction to apply auto-fixes.
- Re-score.
- Repeat up to MAX_ITERATIONS (default 5).
- If still < 17/20 after cap → escalate to user with concrete remaining issues; user decides continue / stop / manual intervention.
COMMIT + PUSH — If files changed during fix loops, run /commit-change (atomic logical commits) then git push.
DEPLOY PAUSE — List exact deploy artifacts: changed files since baseline, deploy hints from project (vercel.json, netlify.toml, Dockerfile, .github/workflows/deploy.yml, etc.), and the deploy process in plain words. Use AskUserQuestion: "Deploy done? (Yes / Not yet / Skip validate)". Block until Yes or Skip.
/web-validate (live site) — Run validator-analyzer against the deployed URL. Capture SCORE_VALIDATE.
GATE — per-axis threshold ≥17/20 — Compute final SCORE_*_AFTER for SEO classique, GEO (IA), HARDEN, VALIDATE. If ANY < 17/20: STOP. Generate .claude/audits/HANDOVER-ROADMAP.md with prioritized analysis of what's blocking each below-threshold axis. Do NOT write the client deliverable. Report to user.
DOC GENERATION (only if all scores ≥17/20) — Read .claude/memory/ registries + full git history. Ask whether to include build/deploy chapter. Synthesize the client deliverable using the 6-chapter structure (BDR-013, full spec in agents/client-handover-writer.md):
- §1 Ce qu'il fallait faire (et pourquoi) — brief + motivation, 100–180 words.
- §2 Résultats — état de santé du site (avant / après) — the score table (SEO classique + GEO + sécurité + conformité, before/after, gated independently at ≥17/20), promoted to the top of the doc for immediate impact.
- §3 Ce qui a été fait — lay summary, ≤300 words, zero technical jargon, no internal tool/skill names (no /seo, /harden, /web-validate, seo-analyzer, etc. — replace with concept names: référencement / sécurité / conformité technique). Forbidden-token grep gate runs before write (covers chapters 1–5).
- §4 Vos informations officielles (NAP) — single source-of-truth table the client reuses across every external platform in §7 (web/local-business only).
- §5 Ce qui vous reste à faire — action-only checklist grouped by cadence (one-time / monthly / quarterly / yearly / when something changes).
- §6 Détails techniques (pour les curieux) — vulgarized BDR decisions, phases with technical detail, optional glossary (score table NOT here — promoted to §2).
- §7 Annexe — plateformes externes (web/local-business only).
- §8 Annexe — build & déploiement (only if requested).
RENDER — Write LIVRAISON.md (fr) or HANDOVER.md (en) at project root, then run scripts/handover-to-pdf.sh to produce the matching branded .html (always) and .pdf (when a PDF engine is on the host: weasyprint > wkhtmltopdf > chromium). HTML/PDF use the ZenQuality cover page, green palette, Inter + Playfair Display typography, running header/footer with project name + page numbers.

Flags:

--skip-fix-loop — run baseline audits once, skip auto-fix iterations.
--max-iterations N — cap fix loop iterations (default 5).
--skip-audits — bypass entire pipeline; jump straight to doc generation from existing audit files.
All previous flags still supported (see argument-hint).

Context from the user (if any): $ARGUMENTS

5.2 KiB Raw Blame History Unescape Escape

5.2 KiB

Raw Blame History