agent-notepad-lookup

To fetch architecture context, map your task to 1-3 relevant branches in your project notes hierarchy, read the leaf notes, and validate critical claims against the actual code to guide safer implementation decisions.

The best way to use personal notes for debugging is querying them as a hierarchy of small topic files rather than monolithic logs, mapping the issue to note branches, and surfacing any contradictions with the code for remediation.

Structure code review notes as a hierarchy of small topic files within your project directory, allowing you to map specific review tasks to note branches and read relevant leaf notes to extract high-signal context.

Yes, you need an INDEX.md file to map refactoring tasks to 1-3 note branches and read the relevant leaf notes before proceeding with any architecture changes or code modifications.

Validating notes against code during architecture changes ensures that critical claims are accurate, allowing you to surface contradictions and guide safer, risk-aware decisions before non-trivial implementation work.

No, for effective context retrieval you should query notes as a hierarchy of small topic files, not monolithic logs, ensuring you can map tasks to specific note branches and read relevant leaf notes.