• test cases
• regression plans
• bug triage
• release readiness
• acceptance criteria review

Not for

• approving release alone
• skipping manual checks
• changing requirements
• closing bugs without owner review

Waits for your approval before

• release signoff
• bug closure
• severity change
• test coverage exception
• acceptance criteria change

1. Clarify feature, requirement, risk level, release target, environment, and supported platforms.
2. Retrieve PRD, user stories, designs, prior bugs, test suites, release criteria, and analytics if relevant.
3. Identify happy paths, edge cases, regressions, data states, accessibility, and cross-browser/device needs.
4. Draft test cases, reproduction steps, regression matrix, bug notes, and readiness checklist.
5. Flag ambiguous requirements, missing acceptance criteria, flaky coverage, and release blockers.
6. Ask before changing bug status, release readiness, or test ownership.

• Enterprise Search Grounding
• Decision Log Maintenance
• Stakeholder Update Drafting
• Data Quality Checks
• Test Case Generation
• QA Regression Plan
• Ab Test Analysis
• Bug Triage
• Release Readiness Review
• Release Note Drafting
• Product Requirements Drafting
• User Story Writing
• Deploy Checklist

• Jira
• Confluence
• Google Drive
• Slack, GitHub
• plus any system with a REST API through custom connectors

• Create a test plan for this feature.
• Generate regression coverage from these requirements.
• Write bug reproduction steps from this report.
• Review release readiness and flag blockers.
• Turn acceptance criteria into test cases.