Skip to content
Back to skills

Ll Resume

ASecurity

Resume from a previous session's continuation prompt

  • 6 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 6, 2026
ai-agentsbashtesting

Security analysis

A100/100

Scanned October 6, 2026

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

Installs into .claude/skills of the current project.

Are you the author of Ll Resume?

Add the live security badge to your README. It updates with every re-scan.

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

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

Download with Pro
SKILL.md
---
name: ll-resume
description: Resume from a previous session's continuation prompt
argument-hint: "[prompt-file]"
allowed-tools:
  - Read
arguments:
  - name: prompt_file
    description: "Path to continuation prompt file (default: .ll/ll-continue-prompt.md)"
    required: false
---

# Session Resume

Resume work from a previous session's continuation prompt.

## Configuration

Read settings from `.ll/ll-config.json` under `continuation`:
- `prompt_expiry_hours`: Hours before prompt is considered stale (default: 24)

## Process

### 1. Locate Continuation Prompt

```bash
PROMPT_FILE="${prompt_file:-.ll/ll-continue-prompt.md}"
```

Check for continuation state in order:
1. Use provided `prompt_file` if specified
2. Check `$(pwd)/.ll/ll-continue-prompt.md` (primary location — project-level)
3. Check `~/.ll/ll-continue-prompt.md` (user-level — warn if found here but not at project-level)
4. Check `.ll/ll-session-state.json` (fallback for metadata)

**Path guard**: If the file is found at `~/.ll/ll-continue-prompt.md` but NOT at the project-level path, display this warning before displaying the prompt content:

```
⚠ Warning: Continuation prompt found at ~/.ll/ll-continue-prompt.md (user-level), not at
  <project-root>/.ll/ll-continue-prompt.md (project-level). This may be caused by a prior
  handoff bug. The prompt may belong to a different project. Proceeding anyway.
```

### 2. Validate Prompt

If continuation prompt found:

- **Check file exists**: Read the file content
- **Check freshness**: Compare file modification time to current time
  - Warn if older than `prompt_expiry_hours` (default: 24)
  - Still allow resume, but note staleness

### 3. Display Resume Context

#### If Continuation Prompt Found (Fresh)

First, check whether the prompt uses the **structured schema** (has `## Intent` and `## Next Steps` sections) or the **legacy prose schema** (has `## Conversation Summary` / `## Resume Point`).

**For structured schema** (preferred — extract and surface key fields):

```
Resuming from previous session
─────────────────────────────────────────────────────────────────

Intent:       [Content of ## Intent section]

Next Steps:
  1. [First item from ## Next Steps]
  2. [Second item from ## Next Steps]
  ...

─────────────────────────────────────────────────────────────────
[Display full continuation prompt content]
─────────────────────────────────────────────────────────────────
```

**For legacy prose schema** (fallback — display full content without extraction):

```
Resuming from previous session
─────────────────────────────────────────────────────────────────

[Display full continuation prompt content]

─────────────────────────────────────────────────────────────────
```

**Then immediately continue with the work described in the prompt.** Do not ask what to do - execute the next steps specified in the continuation prompt.

#### If Continuation Prompt Found (Stale)

Apply the same structured vs. legacy detection above, then:

```
Resuming from previous session (stale: <N> hours old)
─────────────────────────────────────────────────────────────────

[Structured summary header OR full legacy content]

─────────────────────────────────────────────────────────────────

Note: This continuation prompt is over <N> hours old.
      Some context may be outdated.
```

**Then immediately continue with the work described in the prompt.** Do not ask what to do - execute the next steps. If context is too stale to be actionable, state what's unclear and proceed with what can be determined.

#### If Only State File Found

```
Previous session state found
────────────────────────────
  Issue:  [active_issue or "None"]
  Phase:  [phase or "Unknown"]
  Todos:  [count] pending items
  Plan:   [plan_file or "None"]

No continuation prompt available.
Consider running /ll:handoff to create one.
```

#### If Nothing Found

```
No continuation state found.

To create a handoff point:
  /ll:handoff              Generate continuation prompt
  /ll:handoff "context"    With explicit context description

Continuation prompts are created by:
  - /ll:handoff command (manual)
  - PreCompact hook (automatic before context compaction)
```

---

## State File Format

The `.ll/ll-session-state.json` file contains:

```json
{
  "timestamp": "ISO 8601 timestamp",
  "active_issue": "ISSUE-ID or null",
  "phase": "planning|implementing|testing|committing|completing or null",
  "plan_file": "path/to/plan.md or null",
  "todos": [
    {"content": "description", "status": "pending|in_progress|completed"}
  ],
  "context": "brief description",
  "handoff_prompt": ".ll/ll-continue-prompt.md"
}
```

---

## Arguments

$ARGUMENTS

- **prompt_file** (optional, default: `.ll/ll-continue-prompt.md`): Path to continuation prompt file
  - If provided, reads from specified path
  - If omitted, checks default location then falls back to state file

---

## Examples

```bash
# Resume from default location
/ll:resume

# Resume from custom prompt file
/ll:resume thoughts/shared/plans/my-handoff.md

# Resume from a specific path
/ll:resume .ll/backup-continue-prompt.md
```

---

## Integration

- Reads prompts created by `/ll:handoff`
- Works with automation state files from `ll-auto` and `ll-parallel`
- Prompts older than `prompt_expiry_hours` are marked as stale but still usable

Attribution

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

Loading comments…