spelunk: understand before touching

Your output is context other skills consume. The map must be compact enough to inject later without tax, and every claim in it must be tied to a real file path you actually saw.

When to use

• "how does this codebase even work"
• "where is authentication handled in this repo"
• "map out this repository before we change anything"

When NOT to use

• PROJECT_CONTEXT.md covers the need and relevant source still agrees: use it as a lead; check the affected path before relying on a sensitive claim.
• The question is answerable by reading one obvious file. Just read it.
• Empty or greenfield repository: say that and stop.