Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
53 commits
Select commit Hold shift + click to select a range
6c7b664
feat: QCSD agents implementation with testability scorer skill
fndlalit Nov 30, 2025
f71361b
fix: Testability-scorer auto-open now works in all environments
fndlalit Dec 1, 2025
32773b1
fix: Stop claiming browser auto-opened when it didn't
fndlalit Dec 1, 2025
a634ea4
fix: Implement one-click browser opening for testability reports
fndlalit Dec 1, 2025
18ce367
docs: Add browser opening documentation for testability-scorer
fndlalit Dec 1, 2025
a593d36
feat: enhance testability-scorer with JSON format normalization
fndlalit Dec 1, 2025
f26e852
Fix testability-scorer to use 10 Testability Principles framework
fndlalit Dec 1, 2025
1cee399
Fix testability-scorer automated script error handling
fndlalit Dec 1, 2025
71cd16f
Fix testability-scorer to work flawlessly with robust error handling
fndlalit Dec 1, 2025
6bf624f
Remove standalone testability-scorer tests - use skill only
fndlalit Dec 1, 2025
eed0290
Enhance testability-scoring skill with comprehensive contextual recom…
fndlalit Dec 1, 2025
577172e
Merge remote-tracking branch 'origin/main' into QCSD-agents
fndlalit Dec 1, 2025
80f3b23
Add browser auto-open to HTML report generator
fndlalit Dec 1, 2025
d9ef8ef
Add run-assessment.sh shell script to testability-scoring skill
fndlalit Dec 1, 2025
daf31d2
Add complete QX Partner Agent implementation with tests and examples
fndlalit Dec 1, 2025
4028ee5
Add QX Partner Agent implementation summary document
fndlalit Dec 1, 2025
6bb20cd
Add QX Partner Agent working demonstration and test scripts
fndlalit Dec 1, 2025
8386240
Rename and generalize QX analysis test scripts
fndlalit Dec 1, 2025
2b860bf
Implement real QX analysis with Playwright browser automation
fndlalit Dec 1, 2025
8afb291
PRODUCTION-READY: QX Partner Agent now matches manual report quality
fndlalit Dec 1, 2025
c5e9126
Add HTML report generator for QX assessments
fndlalit Dec 1, 2025
210e91e
feat(qx): Implement three-pronged QX analysis solution
fndlalit Dec 1, 2025
66b1d3a
docs(qx): Add comprehensive solution summary
fndlalit Dec 1, 2025
e364e57
Merge branch 'main' into QCSD-agents
proffesor-for-testing Dec 2, 2025
e78f913
Merge branch 'main' into QCSD-agents
proffesor-for-testing Dec 2, 2025
7cd1050
fix(qx): Comprehensive QX analysis improvements
fndlalit Dec 2, 2025
186b026
Merge branch 'QCSD-agents' of https://github.com/fndlalit/agentic-qe …
fndlalit Dec 2, 2025
44dba50
Merge upstream/main into QCSD-agents - Resolve conflicts
fndlalit Dec 2, 2025
5d598c3
Merge upstream/main into QCSD-agents
Dec 23, 2025
99e5557
Merge: resolve conflicts in v2/reports/ files
Jan 25, 2026
b94c072
Merge remote-tracking branch 'origin/main' into QCSD-agents
Jan 25, 2026
aded719
fix(skills): rewrite QCSD Ideation Swarm to actually work
Jan 25, 2026
76b11b1
feat(qcsd-ideation-swarm): v6.1 with strict enforcement and Task tool…
Jan 25, 2026
e1aed25
feat(qcsd-ideation-swarm): v7.0 with DDD domain integration and multi…
Jan 25, 2026
122eb2b
docs(qcsd): add cross-phase feedback loop analysis and memory impleme…
Jan 25, 2026
50dc1aa
feat(v3): implement cross-phase memory system for QCSD feedback loops
Jan 25, 2026
72ed1cd
docs: update cross-phase memory doc to reflect actual implementation
Jan 25, 2026
54e9017
feat(v3): integrate cross-phase memory with MCP server + add tests
Jan 25, 2026
b2066ce
docs: update cross-phase memory doc to v1.2 with full integration status
Jan 25, 2026
f890e2b
feat(cross-phase): complete QCSD feedback loop integration
Jan 25, 2026
a184016
docs(demo): add 10-minute QCSD presentation script
Jan 25, 2026
9a80cd8
docs(demo): update to use Playwright E2E tests
Jan 25, 2026
ac2b48a
docs(demo): target real e-commerce site sauce-demo.myshopify.com
Jan 25, 2026
a8498ef
docs(demo): add single Queen command orchestration option
Jan 25, 2026
37090e6
docs(demo): reorder to logical sequence - tests generated last
Jan 25, 2026
85e5760
feat(a11y-ally): add v7.0 parallel resilient multi-tool scan
Jan 26, 2026
e6d1fda
feat(qcsd): implement QCSD Ideation Swarm workflow
Jan 27, 2026
87a415c
chore: reorganize QCSD and N8N documentation
Jan 27, 2026
7494076
feat(qcsd): wire MCP task_orchestrate to auto-execute workflows
Jan 27, 2026
37ffeee
Merge remote-tracking branch 'origin/main' into QCSD-agents
Jan 27, 2026
3d1e784
feat(qcsd): add live website URL support for QCSD Ideation Swarm
Jan 27, 2026
050e40e
feat(qcsd): enforce proper skill invocation with flag detection and c…
Jan 27, 2026
3cab30a
feat(qcsd): add QCSD analysis exclusion, E2E test framework, and n8n …
Jan 27, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
100 changes: 100 additions & 0 deletions .claude/agents/v3/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,100 @@
# AQE V3 Agents Index

This directory contains V3 QE agents installed by `aqe init`.

> **Note**: This directory only contains AQE-specific agents (v3-qe-*).
> Claude-flow core agents (adr-architect, memory-specialist, etc.) are part of
> the claude-flow system and are available separately.

## Summary

- **Total Agents**: 1
- **V3 QE Domain Agents**: 1
- **V3 Subagents**: 0

## V2 → V3 Migration Guide

| V2 Agent | V3 Agent | Domain | Key Changes |
|----------|----------|--------|-------------|
| `qe-a11y-ally` | `qe-accessibility-auditor` | visual-accessibility | **MANDATORY video pipeline** |
| `qe-test-generator` | `qe-test-architect` | test-generation | ReasoningBank learning |
| `qe-coverage-analyzer` | `qe-coverage-specialist` | coverage-analysis | O(log n) sublinear |
| `qe-coordinator` | `qe-learning-coordinator` | learning-optimization | Cross-domain patterns |
| `qe-flaky-investigator` | `qe-flaky-hunter` | defect-intelligence | ML-powered detection |

## Critical: qe-accessibility-auditor

The V3 accessibility auditor has a **MANDATORY video accessibility pipeline**.

### V2 Behavior (qe-a11y-ally)

Generated these files when videos detected:
- `*-captions.vtt` - For deaf/hard-of-hearing users
- `*-audiodesc.vtt` - For blind/low-vision users
- Implementation instructions

### V3 Behavior (qe-accessibility-auditor)

**MUST** execute the same pipeline:

1. **Detect** - Find `<video>`, `<iframe>` elements
2. **Download** - `curl -L -o video.mp4 URL`
3. **Extract** - `ffmpeg -vf "fps=1/3" -frames:v 10`
4. **Analyze** - Read each .jpg with Claude Vision
5. **Generate** - Create .vtt from actual descriptions
6. **Save** - Output to `docs/accessibility/captions/{page-slug}/`

### Expected Output Structure

```
docs/accessibility/captions/{page-slug}/
├── video-001-captions.vtt # Captions
├── video-001-audiodesc.vtt # Audio descriptions
├── implementation.md # HTML integration
└── audit-report.md # WCAG report
```

### Invocation

Use the skill for guaranteed video pipeline execution:

```
/qe-a11y-ally https://example.com/page
```

Or via Task with explicit video pipeline requirement:

```javascript
Task({
prompt: "Audit accessibility including MANDATORY video pipeline for URL",
subagent_type: "qe-accessibility-auditor"
})
```

## Usage

Spawn agents using Claude Code's Task tool:

```javascript
Task("Generate tests for UserService", "...", "qe-test-architect")
Task("Analyze coverage gaps", "...", "qe-coverage-specialist")
Task("Audit accessibility with video captions", "...", "qe-accessibility-auditor")
```

## V3 QE Domain Agents (1)

Quality Engineering agents mapped to the 12 DDD bounded contexts.

| Agent | Domain | File |
|-------|--------|------|
| `qe-accessibility-auditor` | visual-accessibility | `qe-accessibility-auditor.md` |

## V3 Subagents (0)

Specialized sub-task agents for TDD and code review.

*None installed*

---

*Updated 2026-01-26 - Added V2→V3 migration guide and video pipeline documentation*
123 changes: 112 additions & 11 deletions .claude/agents/v3/qe-accessibility-auditor.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,17 +53,118 @@ Proceed with testing without confirmation when standards are clear.
Apply multi-tool testing by default for comprehensive coverage.
Generate remediation guidance with code examples automatically.

**Video Accessibility Pipeline (MANDATORY for pages with videos):**
1. Extract video URLs using Playwright/network interception
2. Download videos locally with curl/ffmpeg
3. Extract frames: `ffmpeg -i video.mp4 -vf "fps=1/3" -frames:v 10 frame_%02d.jpg`
4. Analyze each frame with Claude Vision (Read tool on .jpg files)
5. Generate WebVTT captions from ACTUAL frame descriptions
6. Generate audio descriptions for blind users
7. Save files to `docs/accessibility/captions/` ready to deploy

**NEVER skip video analysis when videos are detected.**
**NEVER generate generic/template captions - use actual frame descriptions.**
## CRITICAL: VIDEO ACCESSIBILITY PIPELINE

**This pipeline is MANDATORY when ANY video is detected on the page.**
**Failure to execute this pipeline is a CRITICAL ERROR.**

### Detection Phase
Look for these video indicators in fetched HTML:
- `<video>` elements with `src` or `<source>` children
- `<iframe>` with YouTube/Vimeo/Wistia URLs
- `video-container`, `video-player` class elements
- JavaScript video players (Video.js, Plyr, etc.)

### Execution Phase (FOR EACH VIDEO)

**Step 1: Download Video**
```bash
# Create working directory
mkdir -p /tmp/a11y-video-work

# For direct MP4/WebM URLs
curl -L -o /tmp/a11y-video-work/video-001.mp4 "VIDEO_URL"

# For YouTube (if yt-dlp available)
yt-dlp -f "best[height<=720]" -o /tmp/a11y-video-work/video-001.mp4 "YOUTUBE_URL" 2>/dev/null || echo "yt-dlp not available"
```

**Step 2: Extract Frames**
```bash
mkdir -p /tmp/a11y-video-work/frames-001
ffmpeg -i /tmp/a11y-video-work/video-001.mp4 \
-vf "fps=1/3" \
-frames:v 10 \
/tmp/a11y-video-work/frames-001/frame_%02d.jpg \
2>/dev/null
```

**Step 3: Analyze Each Frame with Claude Vision**
Use the Read tool on EACH extracted .jpg file:
```
Read /tmp/a11y-video-work/frames-001/frame_01.jpg
Read /tmp/a11y-video-work/frames-001/frame_02.jpg
Read /tmp/a11y-video-work/frames-001/frame_03.jpg
... (continue for all 10 frames)
```

For each frame, document:
- Scene: Setting, environment, lighting conditions
- People: Who is present, what they're doing, expressions
- Objects: Products, props, vehicles, equipment
- Text: Any visible text, logos, signs, labels
- Action: What's happening, movement, transitions
- Colors: Dominant colors, contrasts, accessibility-relevant

**Step 4: Generate WebVTT Captions**
```vtt
WEBVTT
Kind: captions

00:00:00.000 --> 00:00:03.000
[Description from frame_01.jpg analysis]

00:00:03.000 --> 00:00:06.000
[Description from frame_02.jpg analysis]

00:00:06.000 --> 00:00:09.000
[Description from frame_03.jpg analysis]
```

**Step 5: Generate Audio Descriptions**
```vtt
WEBVTT
Kind: descriptions

00:00:00.000 --> 00:00:03.000
SCENE: [Detailed scene description for blind users]
VISUAL: [What's on screen]
TEXT: [Any readable text]
ACTION: [What's happening]
```

**Step 6: Save Output Files**
```bash
# Create output directory
mkdir -p docs/accessibility/captions/{page-slug}

# Save generated files
# - video-001-captions.vtt
# - video-001-audiodesc.vtt
# - implementation.md (HTML code examples)
```

### Enforcement Rules

1. **NEVER** complete an accessibility audit without checking for videos
2. **NEVER** skip the video pipeline if videos are detected
3. **NEVER** generate placeholder/template captions - use ACTUAL frame analysis
4. **ALWAYS** use the Read tool on actual .jpg frame files for Vision analysis
5. **ALWAYS** save output to `docs/accessibility/captions/{page-slug}/`
6. **ALWAYS** include implementation instructions in the output

### Validation Checklist (Self-Check Before Completing)

- [ ] Did I check for `<video>` and `<iframe>` elements?
- [ ] Did I download each detected video?
- [ ] Did I extract frames with ffmpeg?
- [ ] Did I use Read tool on each .jpg frame file?
- [ ] Did I generate captions.vtt from ACTUAL frame descriptions?
- [ ] Did I generate audiodesc.vtt with detailed scene info?
- [ ] Did I save files to docs/accessibility/captions/?
- [ ] Did I include implementation instructions?

**If ANY checkbox is NO and videos were detected, the task is INCOMPLETE.**
</default_to_action>

<parallel_execution>
Expand Down
40 changes: 40 additions & 0 deletions .claude/agents/v3/qe-bdd-generator.md
Original file line number Diff line number Diff line change
Expand Up @@ -257,6 +257,46 @@ Use via CLI: `aqe skills show test-design-techniques`
Use via Claude Code: `Skill("exploratory-testing-advanced")`
</skills_available>

<cross_phase_memory>
**QCSD Feedback Loop**: Quality-Criteria Loop (Development → Ideation)
**Role**: CONSUMER - Receives untestable patterns to avoid in BDD scenarios

### On Startup, Query Quality-Criteria Signals:
```typescript
const result = await mcp__agentic_qe__cross_phase_query({
loop: "quality-criteria",
maxAge: "60d"
});

// Learn from historical untestable patterns
for (const signal of result.signals) {
if (signal.untestablePatterns) {
for (const pattern of signal.untestablePatterns) {
// Never generate scenarios using untestable patterns
avoidPattern(pattern.acPattern);
// Use better patterns in scenario generation
preferPattern(pattern.betterPattern);
}
}
if (signal.recommendations?.acTemplates) {
// Use proven AC templates for scenario generation
addScenarioTemplates(signal.recommendations.acTemplates);
}
}
```

### How to Use Injected Signals:
1. **Pattern Avoidance**: Don't use patterns from `untestablePatterns[].acPattern`
2. **Better Patterns**: Prefer `untestablePatterns[].betterPattern` structures
3. **Templates**: Use `acTemplates` for proven scenario structures
4. **Coverage Gaps**: Generate scenarios that would fill `coverageGaps[].codeArea`

### Signal Flow:
- **Consumes**: Untestable patterns and templates from qe-coverage-specialist, qe-gap-detector
- **Namespace**: `aqe/cross-phase/quality-criteria/ac-quality`
- **Expected Signals**: AC templates and patterns to avoid
</cross_phase_memory>

<coordination_notes>
**V3 Architecture**: This agent operates within the requirements-validation bounded context (ADR-006).

Expand Down
39 changes: 39 additions & 0 deletions .claude/agents/v3/qe-coverage-specialist.md
Original file line number Diff line number Diff line change
Expand Up @@ -206,6 +206,45 @@ Use via CLI: `aqe skills show risk-based-testing`
Use via Claude Code: `Skill("mutation-testing")`
</skills_available>

<cross_phase_memory>
**QCSD Feedback Loop**: Quality-Criteria Loop (Development → Ideation)
**Role**: PRODUCER - Stores untestable patterns from coverage analysis

### On Coverage Gap Detection, Store Quality-Criteria Signal:
```typescript
mcp__agentic_qe__cross_phase_store({
loop: "quality-criteria",
data: {
untestablePatterns: [
{
acPattern: "<acceptance-criteria-pattern>",
problem: "<why-its-untestable>",
frequency: <0.0-1.0>,
betterPattern: "<improved-pattern>"
}
],
coverageGaps: [
{
codeArea: "<file-or-module>",
coveragePercentage: <percentage>,
rootCause: "<why-gap-exists>",
acImprovement: "<how-better-AC-would-help>"
}
],
recommendations: {
forRequirementsValidator: ["<AC improvement recommendations>"],
acTemplates: { "<feature>": "<template>" }
}
}
})
```

### Signal Flow:
- **Produces**: Untestable patterns, coverage gaps → consumed by qe-requirements-validator, qe-bdd-generator
- **Namespace**: `aqe/cross-phase/quality-criteria/ac-quality`
- **TTL**: 60 days (AC quality insights inform story writing)
</cross_phase_memory>

<coordination_notes>
**V3 Architecture**: This agent operates within the coverage-analysis bounded context (ADR-003).

Expand Down
36 changes: 36 additions & 0 deletions .claude/agents/v3/qe-defect-predictor.md
Original file line number Diff line number Diff line change
Expand Up @@ -230,6 +230,42 @@ Use via CLI: `aqe skills show risk-based-testing`
Use via Claude Code: `Skill("mutation-testing")`
</skills_available>

<cross_phase_memory>
**QCSD Feedback Loop**: Strategic Loop (Production → Ideation)
**Role**: PRODUCER - Stores risk weights from production defect analysis

### On Completion, Store Strategic Signal:
```typescript
mcp__agentic_qe__cross_phase_store({
loop: "strategic",
data: {
riskWeights: [
{
category: "<defect-prone-area>",
weight: <0.0-1.0>,
confidence: <0.0-1.0>,
evidence: {
defectCount: <count>,
percentageOfTotal: <percentage>,
severityDistribution: { critical: <n>, high: <n>, medium: <n> },
timeRange: { start: "<date>", end: "<date>" }
}
}
],
recommendations: {
forRiskAssessor: ["<recommendations for risk assessment>"],
forQualityCriteria: ["<recommendations for acceptance criteria>"]
}
}
})
```

### Signal Flow:
- **Produces**: Production risk weights → consumed by qe-risk-assessor, qe-quality-criteria-recommender
- **Namespace**: `aqe/cross-phase/strategic/production-risk`
- **TTL**: 90 days (strategic insights have long-term value)
</cross_phase_memory>

<coordination_notes>
**V3 Architecture**: This agent operates within the defect-intelligence bounded context (ADR-006).

Expand Down
Loading
Loading