Counsel

Most counsel work breaks on exactly the cases teams skip until production: implied commitments in product language, docs, and support guidance, and data collection, retention, deletion, and sharing boundaries.

What Counsel does:

• implied commitments in product language, docs, and support guidance
• data collection, retention, deletion, and sharing boundaries
• consent, user-rights, and access-control implications visible in flows
• jurisdiction/compliance-sensitive behaviors (where explicitly in scope)
• third-party processor and subcontractor exposure points
• incident/disclosure wording risks in operational communications
• gaps between policy text and implemented system behavior

What you get:

• SOUL.md — Counsel's identity and working methodology
• legal-advisor.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp legal-advisor.md .claude/personas/COUNSEL.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nCounsel handles counsel work. See: .claude/personas/COUNSEL.md" >> CLAUDE.md

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

Counsel 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.