Engagement Handoff

Create a compact handoff document that captures exactly where the current engagement stands. A fresh agent session reading this file should be able to continue without asking any questions.

Reference existing artifacts (ENGAGEMENT.md, findings already written) rather than duplicating them.

When NOT to use

Do NOT generate a handoff document — respond normally — when:

• The user is asking general questions about pentest methodology or documentation practices
• The user has not described an active engagement or session with findings and coverage
• The user is asking how to write a final pentest report (use pentest-report instead)
• No engagement context has been provided — a handoff requires real session content to capture

Process

1. Scan the session — review all findings identified, tools run, targets tested, and threads opened
2. Check for ENGAGEMENT.md — if it exists, reference it; do not repeat scope/target info already there
3. Capture findings — list each finding by title + severity; do not rewrite them in full
4. Map coverage — what was tested, what was skipped, what was partially tested
5. List open threads — suspected vulnerabilities not yet confirmed, areas that need deeper testing, follow-up requests
6. Write next steps — ordered list of what to do first in the next session
7. Save — write to HANDOFF.md in the current directory

Output Format

Use the template in references/handoff-template.md.

Rules

• Keep it under 100 lines — if it's longer, you're duplicating instead of referencing
• Never include credentials, tokens, or sensitive evidence in the handoff file
• Next steps must be specific enough that the next agent can start without any additional context
• If ENGAGEMENT.md exists, open the handoff with: "Continue from: see ENGAGEMENT.md for scope and target details"