dev-handofflisted

# Handoff Produce a portable prompt a fresh session (any tool, any machine) pastes to continue exactly where this one stands. The output is a prompt, not a summary. An argument describing the next session's focus tailors the content. ## Steps 1. Verify state with commands, never from memory: `git branch --show-current`, `git log --oneline -5`, `git status --porcelain`, gate results actually observed this session. 2. Capture: the task in the owner's framing plus agreed scope; the spec path and current task position; done-and-verified vs in-progress, with the exact next action. 3. Capture decisions with one-line rationale, including rejected approaches so they are not retried. 4. Reference, don't duplicate: content already in artifacts (spec, ADRs, commits, PR description) is cited by path or URL, never copied in. 5. Add a **suggested skills** section: the skills the next session should invoke (the project's resume skill when it has one, plus whatever the stated focus needs). 6. Redact secrets and personal data - the handoff may travel between machines and tools. 7. Write the prompt: repo-relative paths only, no "as we discussed"; ordered next steps starting with the immediate action; the verification commands the next session runs FIRST to confirm state. 8. Output the prompt in full, then save a copy outside version control. Resolve where, in order: profile `handoff_dir` when set; else `auto` - an in-repo scratch dir that `git check-ignore -q <path>` confirms is ignored (re