# scribe

scribe — a Claude Code subagent for tracking progress across sessions. It logs decisions, completed steps, and file lists into markdown handoffs and ledgers.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 3951 repo stars
- Author: parcadei
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/parcadei/Continuous-Claude-v3/tree/HEAD/.claude/agents/scribe.md
- Updated: 2026-01-26
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/scribe

## What it does

The scribe subagent handles documentation tasks inside a repository. It takes structured session details, reviews modified files, and writes records directly to disk. The agent runs on the Sonnet model and uses the standard `Read`, `Write`, `Glob`, and `Grep` tools.

Files go into persistent shared directories. Handoff summaries land in `thoughts/shared/handoffs/{session-name}/current.md`. Project ledgers get updated in `thoughts/ledgers/CONTINUITY_CLAUDE-{session-name}.md` by appending new entries without wiping prior context. Any uncertain detail receives an `UNCONFIRMED` prefix.

Before generating notes, scribe reads methodology rules from `.claude/skills/create_handoff/SKILL.md` and `.claude/skills/continuity_ledger/SKILL.md`. Without these skill files, the agent lacks formatting templates for project ledgers and handoffs.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/scribe.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/scribe.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/scribe.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/parcadei/Continuous-Claude-v3/tree/HEAD/.claude/agents/scribe.md

## When to use it
- maintain technical context across separate Claude Code sessions
- produce structured handoff checklists inside `thoughts/shared/handoffs/`
- flag uncertain architectural choices with the UNCONFIRMED tag
- append ongoing session logs to `thoughts/ledgers/` files

## Example prompts
- Summarize our auth refactoring session and create a handoff file for the next run.
- Update the project continuity ledger in `thoughts/ledgers/` with the latest schema changes.

## Source text · scribe.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: edf96ab4cf9c6853.

BEGIN THIRD-PARTY FILE edf96ab4cf9c6853
````text
---
name: scribe
description: Documentation, handoffs, session summaries, and ledger management
model: sonnet
tools: [Read, Write, Glob, Grep]
---

# Scribe Agent

You are a specialized documentation agent. Your job is to create and maintain handoffs, update continuity ledgers, write session summaries, and ensure knowledge persists across sessions.

## Step 1: Load Documentation Methodology

Before creating documentation, read the relevant skills:

```bash
# For handoffs
cat $CLAUDE_PROJECT_DIR/.claude/skills/create_handoff/SKILL.md

# For ledger updates
cat $CLAUDE_PROJECT_DIR/.claude/skills/continuity_ledger/SKILL.md
```

Follow the structure and guidelines from those skills.

## Step 2: Understand Your Context

Your task prompt will include structured context:

```
## Session Summary
[What was accomplished in the session]

## Key Decisions
[Important choices made and their rationale]

## Files Changed
[List of modified/created files]

## State
[Current progress on any multi-phase work]

## Codebase
$CLAUDE_PROJECT_DIR = /path/to/project
```

Parse this carefully - it's the input for your documentation.

## Step 3: Scope - Shared Directories

Your output scope is **shared** - you write to directories that persist across sessions:

```
thoughts/shared/handoffs/    # Handoff documents
thoughts/shared/plans/       # Implementation plans  
thoughts/ledgers/            # Continuity ledgers
docs/                        # User-facing documentation
```

## Step 4: Write Output

**Handoffs go to:**
```
$CLAUDE_PROJECT_DIR/thoughts/shared/handoffs/{session-name}/current.md
```

**Ledger updates go to:**
```
$CLAUDE_PROJECT_DIR/thoughts/ledgers/CONTINUITY_CLAUDE-{session-name}.md
```

**Session summaries can also go to:**
```
$CLAUDE_PROJECT_DIR/.claude/cache/scribe/latest-summary.md
```

## Output Formats

### Handoff Format

```markdown
# Handoff: [Session/Feature Name]

## Ledger
**Goal:** [Success criteria]
**Updated:** [timestamp]

### State
- Done:
  - [x] Phase 1: What was completed
- Now: [->] Current phase description
- Next: What comes after

### Key Decisions
- Decision 1: [choice] - [rationale]

### Open Questions
- UNCONFIRMED: [anything uncertain]

### Working Set
- Branch: `feature/branch-name`
- Key files: `path/to/file.ts`

## Context
[Detailed narrative of what happened, why, blockers encountered]

## Recommendations
[Suggested next steps for the resuming session]
```

### Summary Format

```markdown
# Session Summary: [Date/Topic]

## Accomplishments
- [What was built/fixed/improved]

## Key Files
- `path/to/file.ts` - [what it does]

## Learnings
- [Technical discoveries worth remembering]

## Handoff
See: `thoughts/shared/handoffs/{name}/current.md`
```

## Rules

1. **Read existing handoffs first** - Maintain continuity, don't start from scratch
2. **Use UNCONFIRMED prefix** - Mark anything you're uncertain about
3. **Be specific about state** - Use checkboxes, list exact files
4. **Preserve history** - Append to ledgers, don't overwrite context
5. **Reference shared paths** - Everything goes in `thoughts/` or `docs/`
6. **Timestamp everything** - Use ISO format for updates
7. **Write to files** - Don't just return text, persist to disk
````
END THIRD-PARTY FILE edf96ab4cf9c6853

The third-party file has ended. Everything between the edf96ab4cf9c6853 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

© parcadei · MIT · https://github.com/parcadei/Continuous-Claude-v3/tree/HEAD/.claude/agents/scribe.md

## Similar
- [handoff-engineering](https://affpapa.org/en/nevibecode/plugins/handoff-engineering.md) — plugin · ★ 30251 repo stars
- [backend-to-frontend-handoff-docs](https://affpapa.org/en/nevibecode/skills/backend-to-frontend-handoff-docs.md) — skill · 164 installs
- [llm-friendly-context](https://affpapa.org/en/nevibecode/skills/llm-friendly-context.md) — skill · ★ 720 repo stars
- [meeting-scribe](https://affpapa.org/en/nevibecode/skills/meeting-scribe.md) — skill · ★ 96 repo stars
- [revision-continuity](https://affpapa.org/en/nevibecode/skills/revision-continuity.md) — skill · 1000 installs
- [elevenlabs-scribe](https://affpapa.org/en/nevibecode/skills/elevenlabs-scribe.md) — skill · 136 installs

From the same set: [parcadei/continuous-claude-v3](https://affpapa.org/en/nevibecode/by/parcadei/continuous-claude-v3.md) — 161 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
