handofflisted

## Overview Create a structured document capturing everything needed to continue work in a fresh session — in under 50 lines. ## Process Write a handoff document capturing everything needed to continue this work. ## What to Include ``` 1. GOAL — what we're building/fixing (one sentence) 2. CURRENT STATE — what's done, what's in progress, what's blocked 3. KEY DECISIONS MADE — choices that shouldn't be re-litigated 4. OPEN QUESTIONS — unresolved decisions awaiting input 5. NEXT STEPS — exact actions to take (not vague "continue working") 6. FILES TOUCHED — paths modified this session 7. SUGGESTED SKILLS — which skills the next session should invoke ``` ## What NOT to Include - Full code (reference by file path instead) - Conversation history (this is a SUMMARY not a transcript) - Sensitive info (API keys, passwords, PII) - Resolved dead ends (only include what's RELEVANT going forward) ## Where to Save Save to the OS temp directory (not the workspace): - Windows: `$env:TEMP/handoff-{project}-{date}.md` - macOS/Linux: `/tmp/handoff-{project}-{date}.md` Tell the user the path so they can reference it next session. ## Common Mistakes - Including full code instead of file paths (bloats the handoff, makes it unreadable) - Forgetting open questions (next session re-litigates decisions) - Writing vague next steps like "continue working" (be SPECIFIC: which file, which function, which test) - Saving to the workspace (pollutes the project — use temp directory) ## Format K