Skip to main content

prepare-a-handoff-note

Prepare a handoff note that transfers current state, decisions, evidence, work in progress, risks, access, contacts, and next actions. Use when responsibility moves between people, teams, shifts, or vendors.

소스 정보

저장소
protosphinx/sphinxstack
최근 소스 활동
2026년 7월 29일 13:55
감지된 SKILL.md 언어
영어
스타
3
포크
0

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
2 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
prepare-a-handoff-note
category
start
description
Prepare a handoff note that transfers current state, decisions, evidence, work in progress, risks, access, contacts, and next actions. Use when responsibility moves between people, teams, shifts, or vendors.
# prepare-a-handoff-note Write for someone who was not present and must act safely. ## When to use - Use for project, operations, incident, leave, shift, vendor, or role transitions. - Do not put passwords, private keys, or unnecessary sensitive data in the note. ## Procedure 1. Identify scope, outgoing owner, incoming owner, handoff time, overlap, and acceptance authority. 2. State current status, last verified evidence, important changes, and what is not complete. 3. List active work with owner, state, next action, deadline, dependency, and source link. 4. Summarize decisions, assumptions, risks, issues, exceptions, and escalation triggers. 5. Link systems, documents, dashboards, runbooks, contacts, and approved access-request paths. 6. Describe near-term calendar events, irreversible actions, and safe stop conditions. 7. Walk through the note, answer questions, verify access independently, and record acceptance. ## Done - A handoff note records scope, verified state, work, decisions, risks, links, contacts, access paths, next actions, and unknowns - Incoming-owner, source-link, access, deadline, escalation, walkthrough, and acceptance checks verify continuity
GitHub에서 보기