Update to Codex Dev Workflows

{
  "description": "Create a concise, evidence-based handoff that lets the next development session continue safely without re-discovering context.",
  "included_files": [],
  "name": "session-handoff",
  "skill_md_contents": "---\nname: session-handoff\ndescription: Create a concise, evidence-based handoff that lets the next development session continue safely without re-discovering context.\n---\n\n# Session handoff workflow\n\nUse this skill at the end of a development session, before delegating work, or when context must move to another agent/person. Inspect the actual working tree, relevant task notes, tests run, and known failures before writing the handoff. Do not manufacture progress from intent.\n\n## Capture the minimum useful context\n\n1. State the task goal and current status.\n2. List completed work and the evidence that it is complete.\n3. Identify changed files/components and the reasoning behind material decisions.\n4. Record tests/checks run, results, and anything not run with the reason.\n5. List outstanding work in priority order, with exact next steps and dependencies.\n6. Call out blockers, risks, unresolved questions, environment assumptions, and safe reproduction/verification steps.\n7. Note uncommitted changes or repository state when relevant.\n\n## Handoff quality rules\n\n- Be concrete enough for another session to continue without guessing.\n- Link to authoritative docs/files rather than duplicating long content.\n- Separate confirmed facts from hypotheses and recommendations.\n- Never claim a release, test pass, or bug fix without evidence.\n- Do not include secrets, credentials, or sensitive user data.\n\n## Final format\n\nUse headings: Goal; Current status; Completed; Validation; Next steps; Risks/blockers; Files/context. Keep it compact and actionable.\n\n"
}