qaa-agent 1.6.2 → 1.6.3

package/.claude/skills/qa-workflow-documenter/SKILL.md

@@ -1,87 +1,87 @@
----
-name: qa-workflow-documenter
-description: QA Workflow Documenter. Generates structured QA workflow documentation with decision trees, playbooks, and AI interaction protocols. Use when user wants to document QA processes, create testing playbooks, define workflow steps, document QA procedures, create decision trees for testing, or standardize QA processes. Triggers on "document workflow", "QA process", "testing playbook", "workflow documentation", "QA procedures", "decision tree", "standardize process", "document QA steps".
----
-
-# QA Workflow Documenter
-
-## Purpose
-
-Generate structured, AI-specific QA workflow documentation with decision trees, playbooks, and AI interaction protocols. Every step answers: WHO does it, WHAT they do, WHAT input they need, WHAT output they produce.
-
-## Core Principle
-
-**AI-first language**: Use precise verbs — scan, extract, classify, generate, validate. Never use vague terms like "review", "check", "handle".
-
-## Output Artifacts
-
-1. **WORKFLOW_[NAME].md** — Step-by-step workflow with decision gates
-2. **DECISION_TREE.md** — Visual decision trees for key branch points
-3. **AI_PROMPTS_CATALOG.md** — Reusable prompt patterns for each workflow step
-4. **CHECKLIST.md** — Pre/post verification checklists
-
-## Workflow Template Structure
-
-### Header Block
-```markdown
-# Workflow: [Name]
-**Version**: [semver]
-**Applies to**: [project types / tech stacks]
-**Prerequisites**: [what must exist before starting]
-**Estimated duration**: [time range]
-**Actors**: [AI Agent, QA Engineer, Team Lead]
-```
-
-### Step Format
-```markdown
-## Step N: [Name]
-**Actor**: [who executes this step]
-**Input**: [what they receive]
-**Action**: [precise description using action verbs]
-**Output**: [what they produce]
-**Decision Gate**: [condition to proceed vs branch]
-
-### AI Prompt Pattern
-[If this step involves an AI agent, include the prompt template]
-```
-
-## Workflow Types
-
-### 1. Repository Intake Workflow
-New repo arrives -> scan -> classify -> assess risk -> recommend strategy
-
-### 2. Test Case Generation Workflow
-Analysis done -> select targets -> generate cases -> validate -> deliver
-
-### 3. QA Repo Bootstrap Workflow
-Blueprint ready -> create structure -> generate configs -> seed initial tests
-
-### 4. Validation & Bug Triage Workflow
-Tests generated -> run -> classify failures -> fix loop -> report
-
-### 5. Test Maintenance Workflow
-Existing tests -> audit -> prioritize fixes -> apply -> verify
-
-## Decision Tree Format
-
-```markdown
-## Decision: [What decision]
-
-```
-[Question]?
-├── YES → [Action A]
-│   └── [Sub-question]?
-│       ├── YES → [Action A1]
-│       └── NO → [Action A2]
-└── NO → [Action B]
-```
-```
-
-## Quality Gate
-
-- [ ] Every step has Actor, Input, Action, Output
-- [ ] No vague verbs (review → scan + classify, check → validate against criteria)
-- [ ] Decision gates have clear YES/NO branches
-- [ ] AI prompt patterns included for AI-executed steps
-- [ ] Prerequisites listed for every workflow
-- [ ] Output artifacts named and described
+---
+name: qa-workflow-documenter
+description: QA Workflow Documenter. Generates structured QA workflow documentation with decision trees, playbooks, and AI interaction protocols. Use when user wants to document QA processes, create testing playbooks, define workflow steps, document QA procedures, create decision trees for testing, or standardize QA processes. Triggers on "document workflow", "QA process", "testing playbook", "workflow documentation", "QA procedures", "decision tree", "standardize process", "document QA steps".
+---
+
+# QA Workflow Documenter
+
+## Purpose
+
+Generate structured, AI-specific QA workflow documentation with decision trees, playbooks, and AI interaction protocols. Every step answers: WHO does it, WHAT they do, WHAT input they need, WHAT output they produce.
+
+## Core Principle
+
+**AI-first language**: Use precise verbs — scan, extract, classify, generate, validate. Never use vague terms like "review", "check", "handle".
+
+## Output Artifacts
+
+1. **WORKFLOW_[NAME].md** — Step-by-step workflow with decision gates
+2. **DECISION_TREE.md** — Visual decision trees for key branch points
+3. **AI_PROMPTS_CATALOG.md** — Reusable prompt patterns for each workflow step
+4. **CHECKLIST.md** — Pre/post verification checklists
+
+## Workflow Template Structure
+
+### Header Block
+```markdown
+# Workflow: [Name]
+**Version**: [semver]
+**Applies to**: [project types / tech stacks]
+**Prerequisites**: [what must exist before starting]
+**Estimated duration**: [time range]
+**Actors**: [AI Agent, QA Engineer, Team Lead]
+```
+
+### Step Format
+```markdown
+## Step N: [Name]
+**Actor**: [who executes this step]
+**Input**: [what they receive]
+**Action**: [precise description using action verbs]
+**Output**: [what they produce]
+**Decision Gate**: [condition to proceed vs branch]
+
+### AI Prompt Pattern
+[If this step involves an AI agent, include the prompt template]
+```
+
+## Workflow Types
+
+### 1. Repository Intake Workflow
+New repo arrives -> scan -> classify -> assess risk -> recommend strategy
+
+### 2. Test Case Generation Workflow
+Analysis done -> select targets -> generate cases -> validate -> deliver
+
+### 3. QA Repo Bootstrap Workflow
+Blueprint ready -> create structure -> generate configs -> seed initial tests
+
+### 4. Validation & Bug Triage Workflow
+Tests generated -> run -> classify failures -> fix loop -> report
+
+### 5. Test Maintenance Workflow
+Existing tests -> audit -> prioritize fixes -> apply -> verify
+
+## Decision Tree Format
+
+```markdown
+## Decision: [What decision]
+
+```
+[Question]?
+├── YES → [Action A]
+│   └── [Sub-question]?
+│       ├── YES → [Action A1]
+│       └── NO → [Action A2]
+└── NO → [Action B]
+```
+```
+
+## Quality Gate
+
+- [ ] Every step has Actor, Input, Action, Output
+- [ ] No vague verbs (review → scan + classify, check → validate against criteria)
+- [ ] Decision gates have clear YES/NO branches
+- [ ] AI prompt patterns included for AI-executed steps
+- [ ] Prerequisites listed for every workflow
+- [ ] Output artifacts named and described

package/.mcp.json

@@ -1,8 +1,8 @@
-{
-  "mcpServers": {
-    "playwright": {
-      "command": "npx",
-      "args": ["@playwright/mcp@latest"]
-    }
-  }
-}
+{
+  "mcpServers": {
+    "playwright": {
+      "command": "npx",
+      "args": ["@playwright/mcp@latest"]
+    }
+  }
+}

package/CHANGELOG.md

@@ -1,71 +1,71 @@
-
-# Changelog
-
-All notable changes to QAA (QA Automation Agent) are documented here.
-
-## [1.6.0] - 2026-03-25
-
-### Added
-- Playwright MCP server bundled in agent package (`.mcp.json`) -- starts automatically when opening project in Claude Code
-- Persistent locator registry at `.qa-output/locators/` -- accumulates real locators across features over time
-  - Per-feature files: `{feature}.locators.md` -- extracted locators for each feature tested
-  - Central index: `LOCATOR_REGISTRY.md` -- all locators by page, searchable by any command
-- Browser-based locator extraction step in `/create-test` and `/qa-from-ticket` -- navigates live app with Playwright MCP and captures real data-testid, ARIA roles, and labels before generating tests
-- Registry cache: if locators for a feature already exist in the registry, browser extraction is skipped (reuses cached locators)
-- `--app-url` flag added to `/qa-from-ticket`
-- CHANGELOG.md
-
-### Changed
-- `qaa-executor` now reads locator registry (when available) to use real locators in POMs instead of proposing them
-- `/create-test` flow: checks registry first, then extracts via browser if needed, BEFORE test generation
-- `/qa-from-ticket` workflow: locator extraction step added after source scan, before test case generation
-
-### Removed
-- `/qa-analyze` command (deprecated since v1.4.0, fully replaced by `/qa-map`)
-
-## [1.5.0] - 2026-03-24
-
-### Added
-- Stable release
-
-## [1.4.0]
-
-### Changed
-- Merged `/qa-analyze` into `/qa-map` -- single command for codebase scanning and analysis
-- Consolidated pipeline flow
-
-### Deprecated
-- `/qa-analyze` command (use `/qa-map` instead)
-
-## [1.3.0]
-
-### Added
-- `qa-learner` skill -- persistent preferences from user corrections
-- Preferences saved to `~/.claude/qaa/MY_PREFERENCES.md`
-- Trigger detection for English and Spanish frustration signals
-
-## [1.2.0]
-
-### Added
-- `qaa-codebase-mapper` agent -- 4 parallel focus areas (testability, risk, patterns, existing tests)
-- `qaa-project-researcher` agent -- researches best testing stack and practices
-- 8 codebase map documents produced by mapper
-
-## [1.1.0]
-
-### Added
-- Workflow definitions for all pipeline stages
-- Interactive installer (`npx qaa-agent`)
-- `qaa init` command for per-project initialization
-- npm package distribution
-
-## [1.0.0]
-
-### Added
-- Full QA automation pipeline -- 11 agents, 17 commands, 10 templates, 7 workflows
-- 3 workflow options (dev-only, immature QA, mature QA)
-- 4-layer test validation (syntax, structure, dependencies, logic)
-- Page Object Model generation with CLAUDE.md standards
-- Test ID injection for frontend components
-- Bug detective failure classification
-- Draft PR delivery with branch naming convention
+
+# Changelog
+
+All notable changes to QAA (QA Automation Agent) are documented here.
+
+## [1.6.0] - 2026-03-25
+
+### Added
+- Playwright MCP server bundled in agent package (`.mcp.json`) -- starts automatically when opening project in Claude Code
+- Persistent locator registry at `.qa-output/locators/` -- accumulates real locators across features over time
+  - Per-feature files: `{feature}.locators.md` -- extracted locators for each feature tested
+  - Central index: `LOCATOR_REGISTRY.md` -- all locators by page, searchable by any command
+- Browser-based locator extraction step in `/create-test` and `/qa-from-ticket` -- navigates live app with Playwright MCP and captures real data-testid, ARIA roles, and labels before generating tests
+- Registry cache: if locators for a feature already exist in the registry, browser extraction is skipped (reuses cached locators)
+- `--app-url` flag added to `/qa-from-ticket`
+- CHANGELOG.md
+
+### Changed
+- `qaa-executor` now reads locator registry (when available) to use real locators in POMs instead of proposing them
+- `/create-test` flow: checks registry first, then extracts via browser if needed, BEFORE test generation
+- `/qa-from-ticket` workflow: locator extraction step added after source scan, before test case generation
+
+### Removed
+- `/qa-analyze` command (deprecated since v1.4.0, fully replaced by `/qa-map`)
+
+## [1.5.0] - 2026-03-24
+
+### Added
+- Stable release
+
+## [1.4.0]
+
+### Changed
+- Merged `/qa-analyze` into `/qa-map` -- single command for codebase scanning and analysis
+- Consolidated pipeline flow
+
+### Deprecated
+- `/qa-analyze` command (use `/qa-map` instead)
+
+## [1.3.0]
+
+### Added
+- `qa-learner` skill -- persistent preferences from user corrections
+- Preferences saved to `~/.claude/qaa/MY_PREFERENCES.md`
+- Trigger detection for English and Spanish frustration signals
+
+## [1.2.0]
+
+### Added
+- `qaa-codebase-mapper` agent -- 4 parallel focus areas (testability, risk, patterns, existing tests)
+- `qaa-project-researcher` agent -- researches best testing stack and practices
+- 8 codebase map documents produced by mapper
+
+## [1.1.0]
+
+### Added
+- Workflow definitions for all pipeline stages
+- Interactive installer (`npx qaa-agent`)
+- `qaa init` command for per-project initialization
+- npm package distribution
+
+## [1.0.0]
+
+### Added
+- Full QA automation pipeline -- 11 agents, 17 commands, 10 templates, 7 workflows
+- 3 workflow options (dev-only, immature QA, mature QA)
+- 4-layer test validation (syntax, structure, dependencies, logic)
+- Page Object Model generation with CLAUDE.md standards
+- Test ID injection for frontend components
+- Bug detective failure classification
+- Draft PR delivery with branch naming convention