Protocole de passation pour sdg-skill

VérifiéSûr

À utiliser en fin de session pour fermer proprement le travail et permettre à la session suivante de reprendre sans lire l'historique. Met à jour TASKS.md, STATE.md et docs/decisions.md, puis valide avec le préfixe T<id>:.

Spar Skills Guide Bot
DeveloppementDébutant
1024/07/2026
Claude Code
#handoff#session-handoff#task-tracking#git-commit

Recommandé pour

Notre avis

Termine une session de travail en mettant à jour les fichiers de tâches et d'état, puis en commitant les modifications, afin qu'une future session IA puisse reprendre sans lire l'historique complet.

Points forts

  • Assure une transition propre entre sessions avec tous les fichiers de suivi synchronisés.
  • Évite la perte de progression et réduit le contexte nécessaire à la session suivante.
  • Impose des messages de commit clairs liés aux identifiants de tâche pour la traçabilité.

Limites

  • Dépend du respect du format spécifique de TASKS.md et STATE.md.
  • Ne capture pas les décisions informelles sauf si elles sont ajoutées explicitement à docs/decisions.md.
  • Nécessite une discipline constante de l'utilisateur ou de l'agent pour être exécuté en fin de session.
Quand l'utiliser

Utilisez à la fin de chaque session de travail sur le dépôt sdg-skill pour permettre une reprise sans couture.

Quand l'éviter

Évitez pour des explorations rapides et sans suite, ou lorsqu'aucune continuation future n'est prévue.

Analyse de sécurité

Sûr
Score qualité85/100

The skill only updates markdown files and runs `git add -A` + `git commit` with a prefixed message. No destructive commands, no exfiltration, no network access beyond git. The instructions are straightforward and do not include any obfuscated payloads or dangerous operations.

Aucun point d'attention détecté

Exemples

Handoff at end of session
Handoff, please.
Run handoff protocol
Run the handoff protocol for the sdg-skill repo.
Close out and prepare for next session
Finish up and prepare for next session using the handoff protocol.

name: handoff description: Use at the end of a session in the sdg-skill repo to close out work cleanly so the next session can resume without reading the chat history. Updates TASKS.md / STATE.md, appends to docs/decisions.md if needed, and commits with the right T<id>: prefix. disable-model-invocation: true

Handoff protocol for sdg-skill

Run this when work is complete (or when stopping for the day) so the next session can pick up cleanly via /resume. The goal: every session ends with the repo in a state where git, STATE.md, and TASKS.md all agree.

Steps

  1. Tick TASKS.md. For each task completed in this session, change [ ][x] and append (done <ISO date YYYY-MM-DD>, <commit-sha>) to the same line. Use today's date.

  2. Update STATE.md. Set:

    • Active task — the task you just finished, or None if at a boundary.
    • Last commit — the SHA you're about to create (or just created).
    • Last action — one-line summary of what was done.
    • Next action — the next concrete thing a future session should do (typically the next unblocked task in TASKS.md).
    • Blockers — list any new blockers; clear any that were resolved.
  3. Append to docs/decisions.md ONLY if the work involved an architectural or non-obvious choice that a future contributor would need the rationale for. If it was a routine implementation, skip this step — docs/decisions.md is for ADRs, not changelogs.

  4. Commit.

    git add -A
    git commit -m "T<id>: <one-line summary>"
    
    • Use the task ID being closed (or the most relevant one).
    • One-line subject; keep it under ~70 chars.
    • Include a body only if the change is non-obvious from the diff.

Branch note

  • Small fixes: commit directly to main with the T<id>: prefix.
  • Risky / large changes: you should already be on a feat/T<id>-<slug> branch — push and open a PR for squash-merge instead of committing direct.

Don't

  • Don't tick a task as [x] if its acceptance criteria (Acceptance: line in TASKS.md) was not actually met. Leave it [~] and note the gap in STATE.md.
  • Don't bypass the redact / provenance rules in any handoff commit (those are hard rules in CLAUDE.md).
  • Don't commit key.json, .env*, runs/, or htmlcov/ (already gitignored, but double-check git status).
  • Don't run git push --force or amend commits that are already on main.
Skills similaires