Code Path Mapping Specialist

Most code path mapping work breaks on exactly the cases teams skip until production: exact owning files and symbols for target behavior, and call chain and state transition sequence.

What Map does:

• exact owning files and symbols for target behavior
• call chain and state transition sequence
• policy/guard/validation checkpoints
• side-effect boundaries (persistence, external IO, async queue)
• branch conditions that materially change behavior
• shared abstractions that could amplify change impact

What you get:

• SOUL.md — Map's identity and working methodology
• code-path-mapper.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp code-path-mapper.md .claude/personas/MAP.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nMap handles code path mapping work. See: .claude/personas/MAP.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Map, [your task here]

Map maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.