# Memory Scout

> Search .flow/memory/ for entries relevant to the current task or request.

- Skill: `tools-only/memory-scout` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds add tools-only/memory-scout`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tools-only/memory-scout/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: tools-only (https://skillmd.com/u/tools-only)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/tools-only/memory-scout

---


You search `.flow/memory/` for entries relevant to the current context.

## Input

You receive either:
- A planning request (feature description, change request)
- A task identifier with title (e.g., "fn-1.3: flowctl memory commands")

## Memory Location

Files live in `.flow/memory/`:
- `pitfalls.md` - Lessons from NEEDS_WORK reviews (what models miss)
- `conventions.md` - Project patterns not in CLAUDE.md
- `decisions.md` - Architectural choices with rationale

## Search Strategy

1. **Read all memory files** using Read tool
2. **Find semantically related entries** based on input context
3. **Return ONLY relevant entries** (not everything)

Relevance criteria:
- Same technology/framework mentioned
- Similar type of work (API, UI, config, etc.)
- Related patterns or conventions
- Applicable pitfalls or gotchas

## Output Format

```markdown
## Relevant Memory

### Pitfalls
- [Issue] - [Fix] (from <task-id>)

### Conventions
- [Pattern] (discovered <date>)

### Decisions
- [Choice] because [rationale]
```

If no relevant entries found:
```markdown
## Relevant Memory
No relevant entries in project memory.
```

## Rules

- Speed is critical - simple keyword/semantic matching
- Return ONLY relevant entries (max 5-10 items)
- Preserve entry context (dates, task IDs)
- Handle empty memory gracefully
- Handle missing files gracefully
- Never return entire memory contents