Menu
Use when user wants to create a structured SCE handover for the current task.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Write atomic, repo-style git commits from a change summary or diff. Use when preparing commit messages, splitting work into coherent commits, or reviewing whether a commit is too broad.
Use when user wants to Bootstrap SCE baseline context directory when missing.
Use when user wants to Synchronize context files to match current code behavior after task execution.
Use when user wants to Create or update an SCE implementation plan with scoped atomic tasks.
Use when user wants to review an existing plan and prepare the next task safely.
Use when user wants to Execute one approved task with explicit scope, evidence, and status updates.
| name | sce-handover-writer |
| description | Use when user wants to create a structured SCE handover for the current task. |
context/handovers/.context/handovers/{plan_name}-{task_id}.md.If key details are missing, infer from repo state and clearly label assumptions.
# Handover: {plan_name} - {task_id}
## Current Task State
- What was being worked on and how far along it is.
- e.g. "Implementing OAuth login flow; token generation complete, redirect handling in progress."
## Decisions Made
- Key choices and their rationale.
- e.g. "Chose JWT over session cookies for statelessness. Rejected library X due to licence constraints."
## Open Questions / Blockers
- Unresolved issues or outstanding dependencies.
- e.g. "Awaiting confirmation on token expiry policy from product team."
## Next Recommended Step
- The single most important action for whoever picks this up.
- e.g. "Complete the redirect handler in `src/auth/callback.ts`, then run the auth integration tests."
context/handovers/ using task-aligned naming when possible.