QA Investigation

A persistent, file-backed investigation journal for a specific failing test. This is the execution layer: it resolves a concrete failure. It does not validate strategy or architecture (grill-me-qa) nor generate QA deliverables (qa-manual-istqb).

The core idea: your context window is volatile RAM; the filesystem is persistent disk. Writing goals, evidence, and decisions to markdown prevents context drift during a long investigation.

When to Use This Skill

• A test fails intermittently (flaky) or deterministically (bug), and you need the root cause.
• The investigation spans many tool calls, multiple runs, or more than one session.
• You want a durable record of what you found, decided, and why.

When NOT to Use This Skill

• Authoring a test from scratch — use the relevant automation/framework skill.
• Designing a framework or coverage strategy — strategy validation (grill-me-qa) or artifact generation (qa-manual-istqb).
• Simple questions or quick lookups (fewer than ~5 tool calls).
• General review of non-test production code.