recall

Retrieve project architecture and design details from documentation and codebase exploration.

3|Updated Feb 24, 2026

Search Tags:#architecture #documentation #codebase #information retrieval #project context #design decisions

Ready to run

npx skills add https://github.com/brettbuddin/claude-plugins --skill recall-brettbuddin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: recall
Source: https://github.com/brettbuddin/claude-plugins/tree/main/smith/skills/recall
Command: npx skills add https://github.com/brettbuddin/claude-plugins --skill recall-brettbuddin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you quickly understand the history, architecture, and design decisions of a project by intelligently searching existing documentation and falling back to codebase exploration.

Core Features & Use Cases

Contextual Information Retrieval: Answers general questions about the project's design, architecture, and codebase.
Intelligent Document Prioritization: Prefers relevant existing research and plan documents before exploring the codebase.
Use Case: If you ask "How does the authentication module work?", this skill will first look for relevant documents in your project's research or plan directories, and if not found, it will then search the codebase for answers.

Quick Start

Ask a question about the project's architecture, like "What is the overall system design?".

Frequently Asked Questions about recall

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I understand a codebase's architecture and design decisions quickly?▼

To understand a codebase's architecture quickly, you can query existing project documentation and codebase structure. This approach retrieves design rationale and contextual information by prioritizing research documents before falling back to code exploration.

What's the best way to find out how a specific module works in my project?▼

The best way to find out how a specific module works is to ask a general question about its behavior. The system will first search existing research and plan directories for relevant documentation, and if none is found, it will explore the codebase directly.

Can I retrieve project context and design rationale without manually reading all the code?▼

Yes, you can retrieve project context and design rationale without manually reading all the code. By querying for project specifics, the tool intelligently searches existing documentation and performs codebase exploration to provide quick answers.

Does this approach prioritize existing documentation over codebase exploration?▼

Yes, this approach prioritizes existing documentation over codebase exploration. It prefers relevant existing research and plan documents to explain system design, only falling back to exploring the codebase if the documentation lacks the needed answers.

How do I get explanations for existing behaviors and component interrelations in a project?▼

To get explanations for existing behaviors and component interrelations, you can inquire about project specifics. The system retrieves information about architecture and structure by querying existing documentation, satisfying the need for quick contextual understanding.

When should I use a documentation-first approach for codebase information retrieval?▼

You should use a documentation-first approach for codebase information retrieval when you need quick, contextual understanding of project components. It intelligently searches existing research and plans to explain design decisions before attempting deeper codebase exploration.