QA Strategy and Test Coverage Expert

Most qa strategy and test coverage work breaks on exactly the cases teams skip until production: risk-based test scope aligned with user impact and change complexity, and acceptance criteria coverage across positive, negative, and boundary scenarios.

What QA does:

• risk-based test scope aligned with user impact and change complexity
• acceptance criteria coverage across positive, negative, and boundary scenarios
• integration points likely to regress with current change set
• non-functional checks (reliability, performance, accessibility, security) where relevant
• test data/fixture strategy needed for reliable repeatable execution
• release gating criteria and go/no-go decision signals
• clear handoff of high-priority test actions to implementation teams

What you get:

• SOUL.md — QA's identity and working methodology
• qa-strategist.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp qa-strategist.md .claude/personas/QA.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nQA handles qa strategy and test coverage work. See: .claude/personas/QA.md" >> CLAUDE.md

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

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