qaa-agent 1.0.0 → 1.2.0

package/.claude/commands/qa-analyze.md

@@ -10,51 +10,12 @@ Analysis-only mode. Scans a repository, detects framework and stack, and produce
 - --dev-repo: explicit path to developer repository
 - --qa-repo: path to existing QA repository (produces gap analysis instead of blueprint)
 
-## What It Produces
-
-- SCAN_MANIFEST.md -- file tree, framework detection, testable surfaces
-- QA_ANALYSIS.md -- architecture overview, risk assessment, testing pyramid
-- TEST_INVENTORY.md -- prioritized test cases with IDs and explicit outcomes
-- QA_REPO_BLUEPRINT.md (if no QA repo) or GAP_ANALYSIS.md (if QA repo provided)
-
 ## Instructions
 
 1. Read `CLAUDE.md` -- all QA standards.
-2. Initialize pipeline context:
-   ```bash
-   node bin/qaa-tools.cjs init qa-start [user arguments]
-   ```
-3. Invoke scanner agent:
-
-Task(
-  prompt="
-    <objective>Scan repository and produce SCAN_MANIFEST.md</objective>
-    <execution_context>@agents/qaa-scanner.md</execution_context>
-    <files_to_read>
-    - CLAUDE.md
-    </files_to_read>
-    <parameters>
-    user_input: $ARGUMENTS
-    </parameters>
-  "
-)
-
-4. Invoke analyzer agent:
-
-Task(
-  prompt="
-    <objective>Analyze repository and produce QA_ANALYSIS.md, TEST_INVENTORY.md, and blueprint or gap analysis</objective>
-    <execution_context>@agents/qaa-analyzer.md</execution_context>
-    <files_to_read>
-    - CLAUDE.md
-    - .qa-output/SCAN_MANIFEST.md
-    </files_to_read>
-    <parameters>
-    user_input: $ARGUMENTS
-    </parameters>
-  "
-)
-
-5. Present results to user. No git operations. No test generation.
+2. Execute the workflow:
+
+Follow the workflow defined in `@workflows/qa-analyze.md` end-to-end.
+Preserve all workflow gates (scan verification, artifact checks).
 
 $ARGUMENTS

package/.claude/commands/qa-from-ticket.md

@@ -7,82 +7,17 @@ Generate test cases and executable test files from a ticket (Jira, Linear, GitHu
 /qa-from-ticket <ticket-source> [--dev-repo <path>]
 
 - ticket-source: one of:
-  - URL to Jira/Linear/GitHub issue (e.g., https://linear.app/team/PROJ-123)
+  - URL to GitHub/Jira/Linear issue
   - Plain text user story or acceptance criteria
   - File path to a .md or .txt with ticket details
 - --dev-repo: path to developer repository (default: current directory)
 
-## What It Produces
-
-- TEST_CASES_FROM_TICKET.md -- test cases derived from acceptance criteria
-- Test spec files (unit, API, E2E as appropriate)
-- Page Object Model files (for E2E tests if needed)
-- Fixture files (test data)
-- Traceability matrix: which test covers which acceptance criterion
-
 ## Instructions
 
 1. Read `CLAUDE.md` -- all QA standards.
+2. Execute the workflow:
 
-2. Parse the ticket source:
-
-   **If URL:** Fetch the ticket content using WebFetch or gh CLI (for GitHub issues).
-   ```bash
-   # GitHub Issues
-   gh issue view <number> --json title,body,labels,assignees
-
-   # For other URLs, use WebFetch to read the page
-   ```
-
-   **If plain text:** Use the text directly as the ticket content.
-
-   **If file path:** Read the file content.
-
-3. Extract from the ticket:
-   - **Title/Summary**: what the feature or bug is about
-   - **Acceptance Criteria**: the specific conditions that must be met (look for "AC:", "Given/When/Then", checkboxes, numbered criteria)
-   - **User Story**: "As a [role] I want [action] so that [benefit]"
-   - **Edge Cases**: any mentioned edge cases, error states, or constraints
-   - **Priority**: ticket priority if available (maps to test priority P0/P1/P2)
-
-4. Read the dev repo source code related to the ticket:
-   - Search for files matching keywords from the ticket title
-   - Read routes, controllers, services, models related to the feature
-   - Identify the actual implementation (or lack of it if the feature is not built yet)
-
-5. Generate test cases that map 1:1 to acceptance criteria:
-   - Each acceptance criterion becomes at least one test case
-   - Add negative tests for each criterion (what should NOT happen)
-   - Add edge case tests if mentioned in the ticket
-   - Every test case follows CLAUDE.md rules: unique ID, concrete inputs, explicit expected outcome
-
-6. Write TEST_CASES_FROM_TICKET.md with:
-   ```markdown
-   # Test Cases from Ticket: [TICKET-ID] [Title]
-
-   ## Source
-   - Ticket: [URL or "manual input"]
-   - Date: [YYYY-MM-DD]
-
-   ## Acceptance Criteria Mapping
-
-   | AC # | Criterion | Test ID(s) | Status |
-   |------|-----------|------------|--------|
-   | AC-1 | [criterion text] | UT-XXX-001, E2E-XXX-001 | Covered |
-   | AC-2 | [criterion text] | API-XXX-001 | Covered |
-
-   ## Test Cases
-   [test cases following CLAUDE.md format]
-   ```
-
-7. Generate executable test files using the qa-template-engine skill.
-
-8. Validate generated tests using the qa-self-validator skill.
-
-9. Present summary:
-   - How many acceptance criteria found
-   - How many test cases generated (by pyramid level)
-   - Traceability: every AC is covered
-   - Any ACs that could not be tested (and why)
+Follow the workflow defined in `@workflows/qa-from-ticket.md` end-to-end.
+Preserve all workflow gates (ticket parsing, traceability, validation).
 
 $ARGUMENTS

package/.claude/commands/qa-gap.md

@@ -9,46 +9,12 @@ Compare a developer repository against its QA repository to identify coverage ga
 - --dev-repo: path to the developer repository (required)
 - --qa-repo: path to the existing QA repository (required)
 
-## What It Produces
-
-- SCAN_MANIFEST.md -- scan of both repositories
-- GAP_ANALYSIS.md -- coverage map, missing tests with IDs, broken tests, quality assessment
-
 ## Instructions
 
 1. Read `CLAUDE.md` -- testing pyramid, test spec rules, quality gates.
-2. Invoke scanner agent to scan both repositories:
-
-Task(
-  prompt="
-    <objective>Scan both developer and QA repositories and produce SCAN_MANIFEST.md</objective>
-    <execution_context>@agents/qaa-scanner.md</execution_context>
-    <files_to_read>
-    - CLAUDE.md
-    </files_to_read>
-    <parameters>
-    user_input: $ARGUMENTS
-    </parameters>
-  "
-)
-
-3. Invoke analyzer agent in gap mode:
-
-Task(
-  prompt="
-    <objective>Produce GAP_ANALYSIS.md comparing dev repo against QA repo</objective>
-    <execution_context>@agents/qaa-analyzer.md</execution_context>
-    <files_to_read>
-    - CLAUDE.md
-    - .qa-output/SCAN_MANIFEST.md
-    </files_to_read>
-    <parameters>
-    user_input: $ARGUMENTS
-    mode: gap
-    </parameters>
-  "
-)
-
-4. Present results. No test generation. No git operations.
+2. Execute the workflow:
+
+Follow the workflow defined in `@workflows/qa-gap.md` end-to-end.
+Preserve all workflow gates (both-repo scanning, gap metrics).
 
 $ARGUMENTS

package/.claude/commands/qa-map.md

@@ -0,0 +1,36 @@
+# QA Codebase Map
+
+Deep-scan a codebase for QA-relevant information. Spawns 4 parallel mapper agents that analyze testability, risk areas, code patterns, and existing tests. Produces structured documents consumed by the QA pipeline.
+
+## Usage
+
+/qa-map [--focus <area>]
+
+- No arguments: runs all 4 focus areas in parallel
+- --focus: run a single area (testability, risk, patterns, existing-tests)
+
+## What It Produces
+
+- TESTABILITY.md + TEST_SURFACE.md — what's testable, entry points, mocking needs
+- RISK_MAP.md + CRITICAL_PATHS.md — business-critical paths, error handling gaps
+- CODE_PATTERNS.md + API_CONTRACTS.md — naming conventions, API shapes, auth patterns
+- TEST_ASSESSMENT.md + COVERAGE_GAPS.md — existing test quality, what's missing
+
+## Instructions
+
+1. Read `CLAUDE.md` — QA standards.
+2. Create output directory: `.qa-output/codebase/`
+3. If no --focus flag, spawn 4 agents in parallel (one per focus area):
+
+For each focus area, spawn:
+
+Agent(
+  prompt="Analyze this codebase for QA purposes. Focus area: {focus}. Write documents to .qa-output/codebase/. Follow the process in your agent definition.",
+  subagent_type="general-purpose",
+  execution_context="@agents/qaa-codebase-mapper.md"
+)
+
+4. If --focus flag, spawn only that one area.
+5. When all complete, print summary of documents produced.
+
+$ARGUMENTS

package/.claude/commands/qa-research.md

@@ -0,0 +1,33 @@
+# QA Research
+
+Research the best testing approach for a project's stack. Investigates framework capabilities, best practices, and testing patterns using official docs and community sources.
+
+## Usage
+
+/qa-research [--mode <mode>]
+
+- No arguments: auto-detects stack and researches testing approach
+- --mode: specific research mode (stack-testing, framework-deep-dive, api-testing, e2e-strategy)
+
+## What It Produces
+
+- TESTING_STACK.md — recommended test framework, assertion libraries, mock strategies
+- FRAMEWORK_CAPABILITIES.md — deep dive into detected test framework
+- API_TESTING_STRATEGY.md — endpoint testing patterns for this stack
+- E2E_STRATEGY.md — E2E approach for the frontend (if detected)
+
+## Instructions
+
+1. Read `CLAUDE.md` — QA standards.
+2. Detect project stack from package.json, requirements.txt, or similar.
+3. Spawn researcher agent:
+
+Agent(
+  prompt="Research the testing ecosystem for this project. Mode: {mode}. Write findings to .qa-output/research/. Follow the process in your agent definition.",
+  subagent_type="general-purpose",
+  execution_context="@agents/qaa-project-researcher.md"
+)
+
+4. Present findings with confidence levels.
+
+$ARGUMENTS

package/.claude/commands/qa-start.md

@@ -14,20 +14,9 @@ Run the complete QA automation pipeline. Analyzes a repository, generates a stan
 ## Instructions
 
 1. Read `CLAUDE.md` -- all QA standards that govern the pipeline.
-2. Read `agents/qa-pipeline-orchestrator.md` -- the pipeline controller.
-3. Invoke the orchestrator:
-
-Task(
-  prompt="
-    <objective>Run complete QA automation pipeline</objective>
-    <execution_context>@agents/qa-pipeline-orchestrator.md</execution_context>
-    <files_to_read>
-    - CLAUDE.md
-    </files_to_read>
-    <parameters>
-    user_input: $ARGUMENTS
-    </parameters>
-  "
-)
+2. Execute the workflow:
+
+Follow the workflow defined in `@workflows/qa-start.md` end-to-end.
+Preserve all workflow gates (stage transitions, checkpoints, error handling, state updates, commits).
 
 $ARGUMENTS

package/.claude/commands/qa-testid.md

@@ -4,51 +4,16 @@ Scan frontend source code, audit missing data-testid attributes, and inject them
 
 ## Usage
 
-/qa-testid <path-to-frontend-source>
+/qa-testid [<source-directory>]
 
-- path-to-frontend-source: directory containing React/Vue/Angular/HTML components
-
-## What It Produces
-
-- TESTID_AUDIT_REPORT.md -- coverage score, missing elements, proposed values by priority
-- Modified source files with data-testid attributes injected
+- source-directory: path to frontend source (auto-detects if omitted)
 
 ## Instructions
 
-1. Read `CLAUDE.md` -- data-testid Convention section for naming rules.
-2. Initialize context:
-   ```bash
-   node bin/qaa-tools.cjs init qa-start --dev-repo [user path]
-   ```
-3. Invoke scanner to identify component files:
-
-Task(
-  prompt="
-    <objective>Scan repository to identify frontend component files</objective>
-    <execution_context>@agents/qaa-scanner.md</execution_context>
-    <files_to_read>
-    - CLAUDE.md
-    </files_to_read>
-    <parameters>
-    user_input: $ARGUMENTS
-    </parameters>
-  "
-)
-
-4. Invoke testid-injector agent:
-
-Task(
-  prompt="
-    <objective>Audit missing data-testid attributes and inject following naming convention</objective>
-    <execution_context>@agents/qaa-testid-injector.md</execution_context>
-    <files_to_read>
-    - CLAUDE.md
-    - .qa-output/SCAN_MANIFEST.md
-    </files_to_read>
-    <parameters>
-    user_input: $ARGUMENTS
-    </parameters>
-  "
-)
+1. Read `CLAUDE.md` -- data-testid Convention section.
+2. Execute the workflow:
+
+Follow the workflow defined in `@workflows/qa-testid.md` end-to-end.
+Preserve all workflow gates (framework detection, user approval, branch creation).
 
 $ARGUMENTS

package/.claude/commands/qa-validate.md

@@ -4,51 +4,17 @@ Validate existing test files against CLAUDE.md standards. Runs 4-layer validatio
 
 ## Usage
 
-/qa-validate <path-to-tests> [--framework <name>]
+/qa-validate [<test-directory>] [--classify]
 
-- path-to-tests: directory or specific test files to validate
-- --framework: override framework auto-detection (playwright, cypress, jest, etc.)
-
-## What It Produces
-
-- VALIDATION_REPORT.md -- pass/fail per file per validation layer, confidence level
-- FAILURE_CLASSIFICATION_REPORT.md -- if failures found, classifies as APP BUG / TEST ERROR / ENV ISSUE / INCONCLUSIVE
+- test-directory: path to test files (auto-detects if omitted)
+- --classify: also run bug-detective to classify failures
 
 ## Instructions
 
 1. Read `CLAUDE.md` -- quality gates, locator tiers, assertion rules.
-2. Invoke validator agent:
-
-Task(
-  prompt="
-    <objective>Validate test files with 4-layer validation and produce VALIDATION_REPORT.md</objective>
-    <execution_context>@agents/qaa-validator.md</execution_context>
-    <files_to_read>
-    - CLAUDE.md
-    </files_to_read>
-    <parameters>
-    user_input: $ARGUMENTS
-    mode: validation
-    </parameters>
-  "
-)
-
-3. If failures detected, invoke bug-detective agent:
-
-Task(
-  prompt="
-    <objective>Classify test failures and auto-fix TEST CODE ERRORS</objective>
-    <execution_context>@agents/qaa-bug-detective.md</execution_context>
-    <files_to_read>
-    - CLAUDE.md
-    - .qa-output/VALIDATION_REPORT.md
-    </files_to_read>
-    <parameters>
-    user_input: $ARGUMENTS
-    </parameters>
-  "
-)
-
-4. Present results. No git operations.
+2. Execute the workflow:
+
+Follow the workflow defined in `@workflows/qa-validate.md` end-to-end.
+Preserve all workflow gates (fix loops, classification).
 
 $ARGUMENTS