• Before ending a long work session
• When user explicitly asks to prepare for continuation
• When context window is filling up
• Before switching to a different task
• When work is blocked and will resume later

1. What was the original goal?
2. What has been accomplished?
3. What is in progress?
4. What is blocked or pending?

• Task 1 - Description
• Task 2 - Description

• Task 3 - Description (current state: ...)

• Task 4 - Description
• Task 5 - Description

undefined

• Found that X depends on Y
• The config in

  .env

  requires Z
• Performance bottleneck in function W

• Waiting for: [API credentials / user decision / review]
• Issue: [Description of blocking problem]

undefined

1. Finish auth refactor
   • File:

     src/auth.ts

   • Remaining: Implement token refresh logic (line 145-160)
   • Reference: See decision about JWT expiry above
2. Add tests
   • File:

     src/auth.test.ts

   • Add tests for:

     refreshToken()

     ,

     validateSession()

1. Update dependent components
   • Files:

     src/middleware/auth.ts

     ,

     src/api/login.ts

   • What: Update to use new auth interface

1. Documentation
   • Update README with new auth flow

undefined

• Completed: [list]
• In progress: [current state]

.claude/context/memory/handoff-[date].md

undefined

• [Task with details]

• [Task] - Current state: [description]

• [Task]

1. [Decision]: [Rationale]

• path/to/file.ts

  - [What was changed]

• [Important finding]

• [Blocker if any]

1. [Concrete action with file/line references]

1. [Next action]

1. Read this handoff document
2. Check status of files mentioned above
3. Start with: [First concrete action]

• .claude/context/memory/learnings.md

  - Project knowledge

• [key file]

  - Current implementation

</instructions>

<examples>
<usage_example>
**User**: "I need to stop for today, prepare a handoff"

**Agent Response**:

```markdown

• Installed NextAuth.js and dependencies
• Created base configuration (

  src/auth.config.ts

  )
• Migrated login endpoint to NextAuth
• Updated session type definitions

• Migrate protected routes - 60% done
  • Completed:

    /dashboard

    ,

    /profile

  • Remaining:

    /settings

    ,

    /admin/*

• Migrate logout flow
• Add OAuth providers (Google, GitHub)
• Update tests

1. Kept custom user table: Didn't use NextAuth's built-in user model because we have existing user data with custom fields.
2. JWT strategy over database sessions: Better for our stateless API architecture.

• src/auth.config.ts

  - New file, NextAuth configuration

• src/middleware.ts

  - Updated to use NextAuth

• src/app/api/auth/[...nextauth]/route.ts

  - NextAuth API route

• The old

  validateToken()

  function is still called by 3 API routes that need updating
• Found hardcoded secret in

  .env.local

  - needs to be rotated

• Need OAuth credentials for Google/GitHub (user to provide)

1. Finish protected route migration
   • File:

     src/middleware.ts

     line 45-60
   • Add

     /settings

     and

     /admin/*

     to protected patterns
2. Update remaining API routes using old auth

   • src/app/api/user/route.ts

     line 12

   • src/app/api/orders/route.ts

     line 8

   • src/app/api/admin/route.ts

     line 15

1. Write tests for new auth
   • Create

     src/__tests__/auth.test.ts

   • Test cases: login, logout, session refresh, protected routes
2. Add OAuth providers (once credentials provided)

1. Read this handoff document
2. Run

   npm run dev

   to verify current state works
3. Start with: Update middleware.ts to protect

   /settings

   route

• src/auth.config.ts

  - Current NextAuth setup

• src/middleware.ts

  - Route protection logic

**Saved to**: `.claude/context/memory/handoff-2024-01-15-auth-refactor.md`

When you resume, use this prompt:

> "Continuing auth refactor. Read `.claude/context/memory/handoff-2024-01-15-auth-refactor.md` and continue from step 1 of Next Steps."

</usage_example>
</examples>

<integration>
**Related Skills**:
- `project-onboarding` - Use when starting fresh on unfamiliar code
- `thinking-tools` - Use think-about-whether-you-are-done before handoff
- `summarize-changes` - Include summary in handoff document
</integration>

.claude/context/memory/learnings.md

• New pattern discovered ->

  .claude/context/memory/learnings.md

• Issue encountered ->

  .claude/context/memory/issues.md

• Decision made ->

  .claude/context/memory/decisions.md

ASSUME INTERRUPTION: If it's not in memory, it didn't happen.