QA Strategy Claw

Try this prompt with QA Strategy Claw to see what it can do:

What a typical QA Strategy Claw report looks like:

# QA Strategy Claw — Assessment Report

**Project**: data-pipeline
**Context**: an ETL pipeline processing 2M events/hour with PostgreSQL and Redis
**Example type**: Illustrative output

## Executive Summary

The QA Strategy Claw completed its review of data-pipeline (an ETL pipeline processing 2M events/hour with PostgreSQL and Redis).
3 findings were identified with concrete remediation steps.
All quality gates were verified before delivery.

## Findings

| # | Severity | Area | Finding | Recommended Action |
|---|----------|------|---------|-------------------|
| 1 | **P0** | Performance | N+1 queries in batch processing loop | Use eager loading with batch size 500 |
| 2 | **P1** | Architecture | Tight coupling between extract and transform | Introduce event queue with dead letter handling |
| 3 | **P2** | Testing | No integration tests for Redis failover | Add chaos test with Redis connection drop |

## Quality Gates

- [✓] test_levels_are_assigned_based_on_risk_and_business_impact
- [✓] smoke_test_suite_covers_all_critical_user_journeys
- [✓] exploratory_testing_charters_are_defined_for_high_risk_areas

## Outputs Generated

- **QA Strategy Document with Risk-Based Test Pyramid**: Included in the report above.
- **Smoke Test Suite for Critical User Journeys**: Included in the report above.
- **Exploratory Testing Charter Pack for High-Risk Features**: Included in the report above.

## Validation

- [x] All quality gates passed (3/3)
- [x] 3 findings documented with severity and remediation
- [x] 3 output sections generated
- [x] Evidence collected and referenced

---
*This is an illustrative example output from FlickClaw. Results vary based on project context.*