handoff

Preserve context across Claude Code sessions by writing a structured HANDOFF.md file at the project root.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "handoff" with this command: npx skills add pfangueiro/claude-code-agents/pfangueiro-claude-code-agents-handoff

Handoff

Preserve context across Claude Code sessions by writing a structured HANDOFF.md file at the project root.

When to Use

  • Before ending a long session

  • Before running /compact to free context

  • When switching to a different task and planning to return

  • When handing work to another developer or agent

How It Works

  • Check if a HANDOFF.md already exists in the project root

  • If it does, read it first to build on previous context

  • Write/update HANDOFF.md with the five sections below

HANDOFF.md Format

Handoff — [Project Name]

Date: YYYY-MM-DD HH:MM Branch: current git branch

Goal

What we're trying to accomplish overall.

Current Progress

  • What's been completed this session
  • Files created or modified (with paths)
  • Decisions made and rationale

What Worked

  • Approaches or patterns that succeeded
  • Key insights discovered

What Didn't Work

  • Approaches tried and abandoned (with reasons)
  • Pitfalls to avoid next time

Next Steps

  1. Specific actionable items for the next session
  2. Ordered by priority
  3. Include file paths and context needed

Rules

  • Always include the current git branch and date

  • Be specific about file paths — the next session has zero context

  • List what didn't work so the next session doesn't repeat failed approaches

  • Keep it under 100 lines — enough to resume, not a novel

  • If a HANDOFF.md exists, update it rather than overwriting blindly

Example

Handoff — checkout-service

Date: 2026-02-12 14:30 Branch: feat/stripe-checkout

Goal

Implement Stripe checkout flow with webhook verification.

Current Progress

  • Created src/api/checkout.ts with createSession endpoint
  • Added src/api/webhooks/stripe.ts for webhook handler
  • Database migration migrations/005_orders.sql applied
  • Unit tests passing for checkout session creation

What Worked

  • Using Stripe's PaymentIntent API instead of Charges (simpler flow)
  • Zod schema validation on webhook payload before processing

What Didn't Work

  • Tried using Stripe Checkout Sessions redirect — didn't work with SPA routing
  • webhook signature verification failed when using raw body parser from express (need raw buffer)

Next Steps

  1. Fix webhook body parsing — use express.raw() middleware for /api/webhooks/stripe
  2. Add idempotency key to prevent duplicate order creation
  3. Write integration tests for the full checkout -> webhook -> order flow
  4. Add error handling for failed payments (update order status)

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

deep-read

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

git-workflow

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

investigate

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

execute

No summary provided by upstream source.

Repository SourceNeeds Review