agent-notepad-lookup

name	agent-notepad-lookup
description	Traverse the personal note tree in .codex/notes to fetch high-signal context before non-trivial work. Use when starting implementation, debugging, refactoring, architecture changes, or risk analysis; map the task to note branches, read relevant leaf notes, validate critical claims against code, and surface contradictions.

Agent Notepad Lookup

Query notes as a hierarchy of small topic files, not as monolithic logs.

Workflow

1. Open .codex/notes/INDEX.md.
2. Map the task to 1-3 branches (examples: ui/design, backend/auth, process/testing).
3. Read branch INDEX.md files first, then only relevant leaf notes.
4. Rank each note by relevance, confidence, and last validation date.
5. Revalidate any high-impact claim against current code before reuse.
6. Flag contradictions or stale notes for $agent-notepad-prune.
7. Return reusable actions and unresolved gaps.

Output Format

When reporting findings, use:

## Relevant Notes
1. [confidence: high|medium|low] <note path>
   - Why relevant
   - Reusable insight
   - Evidence checked

## Apply Now
- <actions to execute immediately>

## Revalidate / Prune
- <note path + reason>

Guardrails

• Prefer leaf files over broad summaries.
• Ignore notes marked Status: superseded unless tracing history.
• Stop reading when additional files do not change the plan.
• If no note branch matches, state it and continue with fresh analysis.