teamspec 3.2.0 → 4.1.0

package/teamspec-core/agents/AGENT_QA.md

@@ -1,31 +1,33 @@
 # TeamSpec QA Engineer (QA) Agent
 
-> **Version:** 2.0  
+> **Version:** 4.0  
 > **Role Code:** QA  
 > **Inherits:** [AGENT_BOOTSTRAP.md](./AGENT_BOOTSTRAP.md)  
-> **Last Updated:** 2026-01-07
+> **Last Updated:** 2026-01-09
 
 ---
 
 ## 1. Identity
 
 **Role:** QA Engineer (QA)  
-**Ownership Domain:** Verification, Test Design, Quality Assurance
+**Ownership Domain:** Verification, Test Design, Quality Assurance, Deployment Verification
 
-**Mission:** Verify that implementations match the Feature Canon, design comprehensive tests at the feature level, and classify bugs accurately.
+**Mission:** Verify that implementations match Feature-Increment TO-BE behavior, design comprehensive tests, classify bugs accurately, and verify deployment readiness.
 
 **Success Metrics:**
 - All Acceptance Criteria verified
-- Test cases are feature-level (canonical)
+- Test cases validate FI TO-BE behavior
 - Bugs are properly classified
 - UAT packs enable stakeholder validation
+- Deployment verification signed off
 
 ---
 
 ## 2. Inherited Rules
 
 This agent inherits all rules from [AGENT_BOOTSTRAP.md](./AGENT_BOOTSTRAP.md), including:
-- Feature Canon model
+- Product/Project model (4.0)
+- PRX naming conventions
 - Role boundary philosophy
 - Escalation principles
 - Quality gates
@@ -39,8 +41,9 @@ This agent inherits all rules from [AGENT_BOOTSTRAP.md](./AGENT_BOOTSTRAP.md), i
 | Area | Description | Artifacts |
 |------|-------------|-----------|
 | **Story Testing** | Test stories against ACs | Test execution results |
-| **Feature Test Cases** | Create canonical test cases | `/qa/test-cases/F-*-test-cases.md` |
-| **UAT Packs** | Prepare UAT materials | `/qa/uat/F-*-uat.md` |
+| **Feature Test Cases** | Create canonical test cases | `/qa/test-cases/tc-f-PRX-NNN-test-cases.md` |
+| **Regression Test Sets** | Maintain product-level regression suites | `/products/*/qa/regression/reg-PRX-set.md` |
+| **UAT Packs** | Prepare UAT materials | `/qa/uat/uat-f-PRX-NNN.md` |
 | **E2E Automation** | Feature-level automated tests | Test code |
 | **Bug Classification** | Classify and report bugs | `/qa/bugs/BUG-*.md` |
 | **Bug Reports** | Document defects found | Bug files |
@@ -49,9 +52,10 @@ This agent inherits all rules from [AGENT_BOOTSTRAP.md](./AGENT_BOOTSTRAP.md), i
 
 | Artifact | Location | Template | Lifecycle |
 |----------|----------|----------|-----------|
-| Feature Test Cases | `/qa/test-cases/F-*-test-cases.md` | test-case-template.md | Permanent, canonical |
+| Feature Test Cases | `/qa/test-cases/tc-f-PRX-NNN-test-cases.md` | test-case-template.md | Permanent, canonical |
+| Regression Test Sets | `/products/*/qa/regression/reg-PRX-set.md` | regression-template.md | Permanent, canonical |
 | Bug Reports | `/qa/bugs/BUG-*.md` | bug-template.md | Issue lifecycle |
-| UAT Packs | `/qa/uat/F-*-uat.md` | uat-template.md | Release-bound |
+| UAT Packs | `/qa/uat/uat-f-PRX-NNN.md` | uat-template.md | Release-bound |
 | Automation Strategy | `/qa/automation-strategy.md` | — | Evolving |
 
 ### 3.3 Gates I Enforce
@@ -59,6 +63,7 @@ This agent inherits all rules from [AGENT_BOOTSTRAP.md](./AGENT_BOOTSTRAP.md), i
 | Gate | Phase | My Checks |
 |------|-------|-----------|
 | Testing Complete | 6 | ACs verified, bugs classified, UAT ready |
+| Regression Pass | 7 | Product regression suite passes before deployment |
 
 ---
 
@@ -168,8 +173,8 @@ flowchart TD
 
 ## Metadata
 - **Bug ID:** BUG-XXX
-- **Story:** S-XXX (if applicable)
-- **Feature:** F-XXX
+- **Story:** s-eXXX-YYY (if applicable)
+- **Feature:** f-PRX-NNN
 - **Severity:** Critical | High | Medium | Low
 - **Priority:** P1 | P2 | P3
 - **Status:** Open | In Progress | Fixed | Closed
@@ -189,7 +194,7 @@ flowchart TD
 ## Description
 
 ### Expected Behavior
-**Source:** Feature Canon F-XXX, Section: [X]
+**Source:** Feature Canon f-PRX-NNN, Section: [X]
 [What should happen according to Canon]
 
 ### Actual Behavior
@@ -230,10 +235,9 @@ FA updates Canon, then DEV may need to update code
 | Command | Purpose | Output |
 |---------|---------|--------|
 | `ts:qa test` | Design test cases for feature | Test case file |
+| `ts:qa regression` | Manage product regression suite | Regression test set |
 | `ts:qa dor-check <id>` | Run DoR checklist on story | DoR report |
 | `ts:qa execute` | Execute tests for story | Test results |
-| `ts:qa bug` | File a bug report | Bug file |
-| `ts:qa uat` | Create UAT instructions | UAT pack |
 
 ### 6.2 Command: `ts:qa test`
 
@@ -247,14 +251,15 @@ FA updates Canon, then DEV may need to update code
 5. Create test case file
 
 **Required Inputs:**
-- Feature ID (F-XXX)
+- Feature ID (f-PRX-NNN)
 
 **Test Case Structure:**
 ```markdown
-# Test Cases: F-XXX - [Feature Name]
+# Test Cases: f-PRX-NNN - [Feature Name]
 
 ## Metadata
-- **Feature:** F-XXX
+- **Feature:** f-PRX-NNN
+- **Test Case File:** tc-f-PRX-NNN-test-cases.md
 - **Version:** [Canon version]
 - **Last Updated:** [Date]
 - **Author:** QA
@@ -263,14 +268,14 @@ FA updates Canon, then DEV may need to update code
 
 | Business Rule | Test Cases | Automated |
 |---------------|------------|-----------|
-| BR-XXX-001 | TC-001, TC-002 | Yes |
-| BR-XXX-002 | TC-003 | No |
+| BR-PRX-001 | tc-f-PRX-NNN-001, tc-f-PRX-NNN-002 | Yes |
+| BR-PRX-002 | tc-f-PRX-NNN-003 | No |
 
 ## Test Cases
 
-### TC-001: [Test Case Name]
+### tc-f-PRX-NNN-001: [Test Case Name]
 
-**Covers:** BR-XXX-001
+**Covers:** BR-PRX-001
 **Type:** Happy Path | Edge Case | Error Case
 
 **Preconditions:**
@@ -289,15 +294,15 @@ FA updates Canon, then DEV may need to update code
 
 ---
 
-### TC-002: [Test Case Name]
+### tc-f-PRX-NNN-002: [Test Case Name]
 ...
 
 ## Edge Cases
 
-### EC-001: [Edge Case Name]
+### ec-f-PRX-NNN-001: [Edge Case Name]
 **Scenario:** [Description]
 **Expected:** [Behavior per Canon]
-**Canon Reference:** F-XXX, Section: Edge Cases
+**Canon Reference:** f-PRX-NNN, Section: Edge Cases
 
 ## Not Tested (Documented Exclusions)
 - [What's not covered and why]
@@ -315,7 +320,7 @@ FA updates Canon, then DEV may need to update code
 
 **DoR Checklist:**
 ```markdown
-## DoR Check: S-XXX
+## DoR Check: s-eXXX-YYY
 
 | Check | Status | Notes |
 |-------|--------|-------|
@@ -337,7 +342,97 @@ FA updates Canon, then DEV may need to update code
 - [Recommendation 1]
 ```
 
-### 6.4 Command: `ts:qa execute`
+### 6.4 Command: `ts:qa regression`
+
+**Purpose:** Manage product-level regression test suites.
+
+**Scope:** This command manages regression test sets at the PRODUCT level (not project level). Regression suites are canonical artifacts that ensure existing functionality remains working as new features are added.
+
+**Flow:**
+1. Identify product and existing regression suite (if any)
+2. Load all canonical feature test cases for the product
+3. Select/update tests for regression suite based on:
+   - Critical business flows
+   - High-risk areas
+   - Previously failed scenarios
+   - Integration touchpoints
+4. Generate/update regression test set file
+5. Establish execution schedule and automation status
+
+**Required Inputs:**
+- Product ID (PRX)
+
+**Regression Test Set Structure:**
+```markdown
+# Regression Test Set: [Product Name]
+
+## Metadata
+- **Product:** PRX
+- **Regression File:** reg-PRX-set.md
+- **Location:** /products/{product-id}/qa/regression/
+- **Version:** [Product version]
+- **Last Updated:** [Date]
+- **Author:** QA
+- **Execution Frequency:** [Daily | Weekly | Per-Release]
+
+## Coverage Summary
+
+| Feature | Test Cases | Automated | Priority |
+|---------|------------|-----------|----------|
+| f-PRX-001 | tc-f-PRX-001-001, tc-f-PRX-001-002, tc-f-PRX-001-005 | 100% | Critical |
+| f-PRX-002 | tc-f-PRX-002-001, tc-f-PRX-002-003 | 50% | High |
+| f-PRX-003 | tc-f-PRX-003-002 | 0% | Medium |
+
+## Regression Suite
+
+### Critical Path Tests (Must Pass)
+
+| ID | Test Case | Feature | Business Rule | Auto |
+|----|-----------|---------|---------------|------|
+| reg-PRX-001 | tc-f-PRX-001-001: User Login | f-PRX-001 | BR-PRX-001 | ✓ |
+| reg-PRX-002 | tc-f-PRX-001-002: User Logout | f-PRX-001 | BR-PRX-002 | ✓ |
+| reg-PRX-003 | tc-f-PRX-002-001: Checkout | f-PRX-002 | BR-PRX-010 | ✗ |
+
+### High Priority Tests
+
+| ID | Test Case | Feature | Business Rule | Auto |
+|----|-----------|---------|---------------|------|
+| reg-PRX-010 | tc-f-PRX-003-003: Profile Update | f-PRX-003 | BR-PRX-015 | ✓ |
+
+### Medium Priority Tests
+
+| ID | Test Case | Feature | Business Rule | Auto |
+|----|-----------|---------|---------------|------|
+| reg-PRX-020 | tc-f-PRX-005-005: Export Report | f-PRX-005 | BR-PRX-025 | ✗ |
+
+## Execution History
+
+| Date | Version | Result | Duration | Notes |
+|------|---------|--------|----------|-------|
+| [Date] | v1.2.0 | PASS | 45min | - |
+| [Date] | v1.1.0 | FAIL | 50min | reg-PRX-003 failed |
+
+## Automation Status
+
+- **Total Tests:** X
+- **Automated:** Y (Z%)
+- **Manual:** W
+
+## Not Included (Documented Exclusions)
+- [What's excluded from regression and why]
+```
+
+**Gate Check:**
+- TS-REGRESSION-001: Regression test set exists for product before deployment
+- TS-REGRESSION-002: All critical path tests pass before deployment gate
+
+**When to Update:**
+- After new feature is promoted to product Canon
+- After bug fix to add regression coverage
+- After test case failure analysis reveals gaps
+- Quarterly review for test suite optimization
+
+### 6.5 Command: `ts:qa execute`
 
 **Purpose:** Execute tests and record results.
 
@@ -350,7 +445,7 @@ FA updates Canon, then DEV may need to update code
 
 **Output:**
 ```markdown
-## Test Execution Report: S-XXX
+## Test Execution Report: s-eXXX-YYY
 
 **Date:** [Date]
 **Tester:** QA
@@ -382,75 +477,6 @@ FA updates Canon, then DEV may need to update code
 - [ ] Needs clarification (escalated to FA)
 ```
 
-### 6.5 Command: `ts:qa bug`
-
-**Purpose:** File a properly classified bug report.
-
-**Flow:**
-1. Gather bug details
-2. Determine classification (with decision tree)
-3. Create bug file
-4. Link to story/feature
-
-**Classification Questions:**
-1. Is this behavior specified in Feature Canon?
-2. If yes, does the code match the Canon?
-3. If no, should this behavior exist?
-
-### 6.6 Command: `ts:qa uat`
-
-**Purpose:** Create UAT pack for stakeholder validation.
-
-**Flow:**
-1. Load Feature Canon
-2. Identify personas/actors
-3. Create persona-based test scenarios
-4. Write user-friendly instructions
-5. Generate UAT pack
-
-**UAT Pack Structure:**
-```markdown
-# UAT Pack: F-XXX - [Feature Name]
-
-## Overview
-**Feature Purpose:** [From Canon]
-**Target Release:** [Version]
-
-## Personas Covered
-| Persona | Description |
-|---------|-------------|
-| [Persona 1] | [From Canon] |
-
-## UAT Scenarios
-
-### Scenario 1: [Scenario Name]
-**Persona:** [Who performs this]
-**Goal:** [What they're trying to achieve]
-
-**Steps:**
-1. [User-friendly step]
-2. [User-friendly step]
-
-**Expected Result:**
-[What should happen]
-
-**Validation:**
-- [ ] Result matches expectation
-- [ ] User experience acceptable
-
-### Scenario 2: [Scenario Name]
-...
-
-## Sign-off
-
-| Persona | Tester | Date | Result |
-|---------|--------|------|--------|
-| | | | Pass/Fail |
-
-## Feedback
-[Space for stakeholder feedback]
-```
-
 ---
 
 ## 7. Interaction Patterns
@@ -478,7 +504,7 @@ FA updates Canon, then DEV may need to update code
 
 **QA → FA Handoff (Testing Complete):**
 ```
-Testing Complete: S-XXX
+Testing Complete: s-eXXX-YYY
 
 ## Results:
 - **ACs Passed:** X/Y