Index

Find and catalog past sessions from the ~/.stoobz/sessions/ archive.

Archive root: Resolve $SESSION_KIT_ROOT (default: ~/.stoobz). All ~/.stoobz/ paths below use this root.

Process

Manifest-First Path (default)

1. •

   Read ~/.stoobz/manifest.json — Parse the sessions array.

2. •

   Apply filter (if user provided an argument):

   • •/index → show all sessions
   • •/index <term> → case-insensitive search across: tags, summary, label, project, branch
   • •Multiple words are ANDed (all must match somewhere across fields)
3. •

   Present the index:

## Session Index — ~/.stoobz/manifest.json (N sessions)

| Project | Date | Label | Summary | Artifacts | Tags |
|---------|------|-------|---------|-----------|------|
| my-project | 2026-02-13 | PROJ-1234 | Auth token refresh fix | T R P | elixir, auth |
| my-project | 2026-02-10 | auth-token-refresh | Token expiry investigation | T H P | elixir, phoenix |
| api-gateway | 2026-01-28 | rate-limiting | API rate limiting | T I | go, infrastructure |

**Legend:** T=TLDR C=Context R=Retro P=Prompt-Lab H=Handoff I=Investigation

Artifact abbreviations:

• •T = TLDR.md
• •C = CONTEXT_FOR_NEXT_SESSION.md
• •R = RETRO.md
• •P = PROMPT_LAB.md
• •H = HANDOFF.md
• •I = INVESTIGATION_SUMMARY.md or INVESTIGATION_CONTEXT.md

1. •

   For each result, show the source_dir so the user can cd there and /pickup.

2. •

   If user is searching, highlight matching results and show the summary field for context.

Deep Search — --deep

When invoked as /index --deep <term> (or /index -d <term>), search inside the actual archived artifact content:

1. •

   Grep ~/.stoobz/sessions/ — Search all .md files under ~/.stoobz/sessions/ for the term (case-insensitive).

2. •

   Group by session — Collect hits by their parent archive directory, not individual files.

3. •

   Present with context snippets:

## Deep Search — "auth-key" (2 hits across 1 session)

### my-app / 2026-02-12-usb-bundle
**TLDR.md:14** — ...the **api-key** rotation wasn't picking up the new value from env...
**INVESTIGATION_CONTEXT.md:87** — ...the **api-key** needs to be passed as a header, not a query param...

Source: ~/my-app
Tags: api, debugging, infrastructure

1. •

   Also run manifest search — Show manifest matches first (fast), then deep matches below. This way the user sees both metadata hits and content hits.

2. •

   If no manifest exists, deep search still works — it's just grep over ~/.stoobz/sessions/.

Filesystem Fallback (no manifest)

If ~/.stoobz/manifest.json doesn't exist:

1. •

   Notify the user: "No manifest found. Falling back to filesystem scan..."

2. •

   Scan ~/.stoobz/sessions/ for directories containing session artifacts (TLDR.md, RETRO.md, PROMPT_LAB.md, HANDOFF.md, INVESTIGATION_SUMMARY.md, INVESTIGATION_CONTEXT.md).

3. •

   For each directory found:

   • •Read the first 5 lines of TLDR.md (if present) for the title and date
   • •Note which artifacts exist
   • •Note the most recent modification date
4. •

   Present the index in the same table format as above (without tags, since those come from the manifest).

5. •

   Suggest: "Run /park --archive-system to build a manifest from these artifacts for faster future lookups. Add --all to skip prompting, or --dry-run to preview first."

Rules

• •Read only headers — Don't load full file contents. The manifest has everything needed; for fallback, first 5 lines of TLDR.md is enough.
• •Sort by date — Most recent first.
• •Fast — This is a lookup tool. Don't analyze, just catalog.
• •Suggest pickup — If a result has a source_dir with CONTEXT_FOR_NEXT_SESSION.md, note: "Has resume context — run /pickup from that directory."
• •Present to the user directly — Don't write a file (this is a query, not an artifact).
• •Manifest is truth — When manifest exists, trust it. Don't re-scan the filesystem.