Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Ll Handoff

ASecurity

Generate continuation prompt for session handoff

6 stars
0 votes
0 copies
0 views
Added 10/6/2026
ai-agentsgobashrefactoringgit

Works with

claude code

Security Analysis

A100/100

Scanned 10/6/2026

$npx -y skills add BrennonTWilliams/little-loops --skill ll-handoff --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ll Handoff?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Ll Handoff
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brennontwilliams-ll-handoff/badge)](https://www.skillsdirectory.com/skills/brennontwilliams-ll-handoff)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: ll-handoff
description: Generate continuation prompt for session handoff
argument-hint: "[context]"
allowed-tools:
  - Read
  - Write
  - Bash(git:*)
arguments:
  - name: context
    description: Brief description of current work context (optional)
    required: false
  - name: flags
    description: "Optional flags: --deep (validate and enrich with git status, todos, recent files)"
    required: false
---

# Session Handoff

Generate a continuation prompt capturing current session state for handoff to a fresh session.

This command uses a **conversation-first approach**: by default, it summarizes the conversation history (which is already in context) without running external commands. Use `--deep` for artifact validation when you need to cross-check conversation against actual disk state.

## Configuration

Read settings from `.ll/ll-config.json` under `continuation`:
- `include_todos`: Include todo list state in deep mode (default: true)
- `include_git_status`: Include git status in deep mode (default: true)
- `include_recent_files`: Include recently modified files in deep mode (default: true)

## Edge Cases

### Compacted Conversations
If the conversation was recently compacted (look for "Conversation was compacted" message):
- Note that summary is based on post-compaction context
- Consider using `--deep` to enrich with artifacts
- Output includes: "Note: Conversation was compacted; summary based on available context"

### Empty or New Sessions
If no meaningful conversation history exists:
- Fall back to artifact-based approach (like `--deep` behavior)
- Output includes: "Note: Fresh session with no prior context"

### Discrepancies (--deep only)
When conversation says one thing but artifacts show another:
- Flag explicitly in Artifact Validation section
- Do not override conversation summary (user may have discussed planned changes)
- Recommend user verify intended changes

## Process

### 1. Summarize the Conversation (Default - Always)

Review the entire conversation history above and extract the four anchored fields:

#### Intent
- **Primary intent**: What was the user trying to accomplish? (1–3 sentences)
- **Scope changes**: Did the user shift focus or refine requirements?

#### File Modifications
- **Files modified**: What files were actually created or changed?
- **What changed**: The specific edit or addition made in each file
- **Why**: The reason the change was made (tied to the issue, user request, or decision)

#### Decisions Made
- **Architectural/design choices**: What patterns or approaches were chosen and why?
- **Explicit rejections**: What alternatives were considered and discarded?
- **User-specified constraints**: Any requirements or constraints the user stated
- **Gotchas discovered**: Things that could trip up the next session

#### Next Steps
- **Immediate action**: The single most important thing to do when resuming
- **Ordered continuation**: 2–5 concrete follow-on actions in priority order
- **Blockers**: Any known blockers or open questions to resolve

### 2. Validate with Artifacts (Only with --deep flag)

**Skip this section if `--deep` flag was NOT provided.**

Parse flags:
```bash
FLAGS="${flags:-}"
DEEP_MODE=false
if [[ "$FLAGS" == *"--deep"* ]]; then DEEP_MODE=true; fi
```

If `DEEP_MODE` is true, run these commands to validate conversation against disk state:

#### Git Status
```bash
git status --short
```
- **Purpose**: Verify actual file state vs what was discussed
- **Check**: Are all mentioned files actually modified?
- **Flag**: Any discrepancies between conversation and disk

#### Todo List
- **Purpose**: Cross-check pending work
- **Verify**: In-progress items match current conversation
- **Include**: All pending items for continuity

#### Recent Modifications
```bash
git diff --name-only HEAD~1 2>/dev/null || git diff --name-only --cached
```
- **Purpose**: Catch files modified outside the conversation flow
- **Include**: Files that may not have been explicitly discussed

#### Plan Files
Check `thoughts/shared/plans/` for:
- Any plan files referenced in conversation
- Most recently modified plan file

#### Discrepancy Detection
Compare conversation claims to artifact reality:
| Conversation Claim | Artifact Reality | Status |
|-------------------|------------------|--------|
| Modified auth.ts | git shows M auth.ts | MATCH |
| Updated tests | No test changes in git | MISMATCH |

### 3. Generate Continuation Prompt

Write to `$(pwd)/.ll/ll-continue-prompt.md` — use an absolute path derived from the current working directory (the project root where Claude Code is running). **Never write to `~/.ll/ll-continue-prompt.md`.**

Before writing, gather the following from the conversation and (in `--deep` mode) from artifacts:

- **session_date**: Today's date in YYYY-MM-DD format
- **session_branch**: Current git branch (from `--deep` artifacts, or infer from conversation)
- **issues_in_progress**: List of issue IDs actively worked on this session (e.g. `[ENH-495]`), or `[]` if none
- **Intent**: 1–3 sentences summarizing what this session was trying to accomplish
- **File Modifications**: Each file actually created or modified, with a brief note on what changed and why
- **Decisions Made**: Each significant decision or architectural choice, with its rationale
- **Next Steps**: Concrete, ordered actions for the next session to continue immediately

**Default mode output** (with or without `--deep` flag):

```markdown
---
session_date: YYYY-MM-DD
session_branch: <branch-name>
issues_in_progress: [ISSUE-ID, ...]
---

# Session Continuation: [Primary Intent from Conversation]

## Intent
[1–3 sentences: what this session was trying to accomplish]

## File Modifications
- `path/to/file.py` — what changed and why
- `path/to/other.md` — what changed and why

## Decisions Made
- Decision: [what was decided] — Rationale: [why]

## Next Steps
1. [First concrete next action]
2. [Second concrete next action]
```

**If `--deep` flag WAS passed** (deep mode):

Include all sections from default mode above, PLUS append this section after `## Next Steps`:

```markdown
## Artifact Validation

### Current Git Status
```
[Output of git status --short]
```

### Discrepancies
[Any differences between conversation and disk state]
- **[File or claim]**: [Conversation said X, disk shows Y]
(If none: "No discrepancies detected between conversation and artifacts")

### Todo List State
| Status | Task |
|--------|------|
| in_progress | [Current task] |
| pending | [Next tasks] |
| completed | [Done tasks] |

### Plan Files
- Active plan: `[path to plan file]`
- Related plans: `[other relevant plan files]`
```

### 4. Output Handoff Signal

After writing the continuation prompt, output:

```
CONTEXT_HANDOFF: Ready for fresh session
Continuation prompt written to: <project-root>/.ll/ll-continue-prompt.md

Source: Conversation summary [+ artifact validation with --deep]

To continue in a new session:
  1. Start a new Claude Code session
  2. Run /ll:resume

Or copy the prompt content above to paste into a new session.
```

---

## Arguments

$ARGUMENTS

- **context** (optional): Brief description of current work context
  - Provides a hint for the conversation summary
  - Example: `"Refactoring authentication module"`

- **flags** (optional): Command behavior flags
  - `--deep` - Validate and enrich with git status, todos, recent files

---

## Examples

```bash
# Generate handoff from conversation summary (default - fast)
/ll:handoff

# Generate handoff with explicit context hint
/ll:handoff "Refactoring authentication module"

# Generate handoff with artifact validation (slower but comprehensive)
/ll:handoff --deep

# Combine context and deep mode
/ll:handoff "Working on BUG-042" --deep
```

---

## Integration

- Complements `/ll:resume` for reading the prompt
- Uses same file format as automation tools (`ll-auto`, `ll-parallel`)
- Outputs `CONTEXT_HANDOFF` signal for automation detection
- Works with PostToolUse context monitor hook for automatic reminders
- PreCompact hook writes `.ll/ll-continue-prompt.md` automatically before context compaction (passive path); `/ll:handoff` is the active/richer manual override

Attribution

BrennonTWilliamsBrennonTWilliams
View sourceSee grades on GitHubMore from BrennonTWilliams →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →