discover

discover

Unified retrieval layer. Aggregates stored memory fragments (what we've decided/learned) and codebase context (what the code actually looks like) into the current session.

When to run

• User types /discover (explicit trigger).
• User says "load context," "prep yourself," "what do you know about X."
• Another skill invokes this one (prep, review).
• Do not auto-fire at session start — explicit invocation only.

Inputs

1. Task text. The most recent user message, plus any arguments passed after /discover.
2. Project root. $CLAUDE_PROJECT_DIR if set, otherwise the current working directory.
3. Optional caller filters (when invoked by another skill, not by a user): scopes, kind, relevance_phases. See "Query interface" below.

Architecture — MCP-primary, skill-fallback

Retrieval is MCP-primary: memory + recap + codemap retrieval is owned by the project-memory MCP engine, out of context. This skill is a thin client over it, with a static always-on floor when the engine is unreachable.

Two responsibilities stay in this skill, NOT the MCP:

• Rules-overlay resolution (§4a) — the rules-overlay tier/patch/disable subsystem is a separate module; v1 keeps it skill-resident.
• The fallback — when the MCP is down, surface the static floor (§0b). The skill does not re-implement the full ranking as its primary path.

0. Primary path — query the MCP engine

Call mcp__project-memory__discover with the task-derived query:

mcp__project-memory__discover({
  cwd: <project root>,     // the engine resolves the layered tier
  include_codemap: true,
  ...                      // remaining params per "Query interface" below
})

The engine returns ranked memory fragments (with 📛 warning prefixes, [related_to] / ⚡ contradicts flags, scope/relevance metadata), plus a ## Codemap block, plus any ⚠️ shadowed-tier / case-split warnings. Surface that result directly (§9 shaping is mostly done by the engine). Then run §4a (rules-overlay) and merge: overlay-resolved rules are appended to the engine's result list and ranked by the same signals the engine reports (scope match, then kind priority, then description keyword overlap with the task); ties break toward the overlay rule, since a tier override outranks a shipped default. The merged list honours the caller's top_n as a single combined cap — overlay rules never bypass the cap. Deliver then renders the merged list's bodies exactly as in the degraded path (§9a applies to engine-returned bodies too).