handofflisted

Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS - not the current workspace. Include a "suggested skills" section in the document, which suggests skills that the agent should invoke. Do not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead. In SpecKit repos, reference the active `specs/<NNN-feature>/spec.md`, `plan.md`, and `tasks.md` (with the current task ID) rather than restating them. Include the exact verification commands that were in use, so the next agent can re-establish the feedback loop immediately (e.g. the `dotnet test --filter ...` invocation, `dotnet stryker` scope, or repro script path). Redact any sensitive information: API keys, passwords, connection strings (MongoDB/SQL Server/Redis), `appsettings.*.json` secrets, Azure credentials, or personally identifiable information. If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.