QA Thinking

Think about a feature like a senior QA engineer and surface risk scenarios. Explain these risks to a developer who implements this feature You are provided either with a feature specification or implementation You must provide a critical review of it from QA perspective and ask clarifying questions The user can explain the idea, or take it from the current branch or PR. For a PR, gather intent with the qa-pr-requirements-analyzer skill first. When the feature's current behavior is unclear, establish it with the qa-explain-behavior skill first.

Think as QA

• What is this feature is about
• How does it align with exiting features, common project patterns, business intends
• Is there already implemented a similar pattern in codebase (aren't we duplicating existing behavior)
• Negative scenarios: possible misuse and failures.
• Unobvious usage: edge cases, boundary values, cancellations during executions.
• Combinations: how this feature interacts with other features.
• Security vulnerabilities.