## 🚀 Default Engagement Prompt

Use this template to activate the Lead QA Engineer persona for any quality engineering engagement. Copy, fill in the bracketed sections, and submit.

---

**Context:** I need Lead QA Engineer support for [project/feature/release name].

**System Under Test:**
- Product type: [web app / mobile / API / microservices / data pipeline]
- Tech stack: [languages, frameworks, databases, infra]
- Current QA maturity: [none / manual-only / partial automation / mature]

**Scope:**
- What changed: [PR link, feature description, or release notes]
- Acceptance criteria: [paste or summarize]
- Known risks: [areas of concern, previous incidents, tech debt]
- Regulatory/compliance constraints: [if any]

**What I Need From You:** (select one or more)
- [ ] Test strategy & risk assessment
- [ ] Test plan with traceability matrix
- [ ] Specific test cases (manual and/or automated pseudocode)
- [ ] Automation framework recommendation or code review
- [ ] Bug triage / defect report review
- [ ] Release go/no-go assessment
- [ ] Postmortem analysis on escaped defect
- [ ] QA process improvement roadmap

**Constraints:**
- Timeline: [sprint end date / release date]
- Team size: [number of QA + devs]
- Tools in use: [CI, test frameworks, bug tracker]
- Budget for new tooling: [yes/no/limited]

**Deliverable Format:** [test plan doc / bullet list / Gherkin / code / executive summary]

---

### Example Invocation (Pre-filled)

> **Context:** Payment refund API v2 — mid-sprint quality review.
>
> **SUT:** Node.js REST API, PostgreSQL, Redis cache, deployed on AWS ECS. QA maturity: partial automation (unit tests exist, no integration suite).
>
> **Scope:** New idempotent refund endpoint with partial-refund support. Acceptance criteria: supports full/partial refund, returns 409 on duplicate request_id, processes within 2s p95. Known risk: previous double-charge incident in v1. PCI-DSS scope.
>
> **Need:** Test strategy, API test cases, and release recommendation.
>
> **Constraints:** 5 days to sprint end, 1 QA + 4 devs, GitHub Actions + Jest, no new tooling budget.
>
> **Deliverable:** Test plan with risk matrix + executable test case outline in Gherkin.

---

### Quick-Start One-Liners

- "Review this bug report and tell me what's missing before I assign it."
- "Build a risk-based test plan for [feature] given these acceptance criteria."
- "Our CI has 12% flaky tests — diagnose and propose a remediation plan."
- "Should we ship? Here's our open defect list and coverage report."
- "Design a Playwright E2E structure for [app] with authentication and feature flags."
- "Run an escaped-defect postmortem on this incident timeline."