@agentic-qe/v3 3.0.0-alpha.10

package/assets/skills/aqe-v2-v3-migration/skill.md

@@ -0,0 +1,322 @@
+---
+name: aqe-v2-v3-migration
+version: 1.0.0
+description: Migrate Agentic QE projects from v2 to v3 with zero data loss
+author: Agentic QE Team
+tags:
+  - migration
+  - upgrade
+  - v2-to-v3
+  - agentic-qe
+trigger:
+  - migrate from v2 to v3
+  - upgrade agentic-qe
+  - aqe migration
+  - v2 to v3 migration
+---
+
+# AQE v2 to v3 Migration Skill
+
+<default_to_action>
+When migrating from v2 to v3:
+1. ANALYZE current v2 installation
+2. BACKUP all data before any changes
+3. MIGRATE configuration, memory, and patterns
+4. VALIDATE migration success
+5. PROVIDE rollback instructions
+
+**Never delete v2 data without explicit user confirmation.**
+</default_to_action>
+
+## Quick Reference
+
+### Migration Command
+```bash
+# Install v3 alongside v2
+npm install @agentic-qe/v3
+
+# Run migration
+npx aqe-v3 migrate
+
+# Or use this skill
+/aqe-v2-v3-migration
+```
+
+### What Gets Migrated
+
+| Component | v2 Location | v3 Location | Auto-Migrate |
+|-----------|-------------|-------------|--------------|
+| Memory DB | `.agentic-qe/memory.db` | `.aqe-v3/agentdb/` | Yes |
+| Config | `.agentic-qe/config.json` | `.aqe-v3/config.json` | Yes |
+| Patterns | `.agentic-qe/patterns/` | `.aqe-v3/reasoning-bank/` | Yes |
+| Cache | `.agentic-qe/cache/` | `.aqe-v3/cache/` | Optional |
+| Logs | `.agentic-qe/logs/` | `.aqe-v3/logs/` | No (fresh start) |
+
+---
+
+## Migration Checklist
+
+### Pre-Migration
+- [ ] Verify v2 installation exists (`.agentic-qe/` directory)
+- [ ] Check v2 version: `aqe --version` (should be 2.x.x)
+- [ ] Backup current data: `npm run backup` (in v2 project)
+- [ ] Note any custom configurations
+- [ ] Document current test counts and coverage
+
+### During Migration
+- [ ] Install v3: `npm install @agentic-qe/v3`
+- [ ] Run migration: `npx aqe-v3 migrate`
+- [ ] Review migration report
+- [ ] Verify data transferred correctly
+
+### Post-Migration
+- [ ] Run v3 tests: `npx aqe-v3 test`
+- [ ] Check coverage: `npx aqe-v3 coverage`
+- [ ] Verify patterns loaded: `npx aqe-v3 patterns list`
+- [ ] Test MCP integration with Claude Code
+
+---
+
+## Architecture Changes (v2 → v3)
+
+### From Monolithic to DDD
+
+```
+v2 Structure:                    v3 Structure:
+├── src/mcp/tools/              ├── src/domains/
+│   ├── test-*.ts (40+ tools)   │   ├── test-generation/
+│   └── ...                     │   ├── test-execution/
+├── src/core/agents/            │   ├── coverage-analysis/
+│   ├── mixed agents            │   ├── quality-assessment/
+│   └── ...                     │   ├── defect-intelligence/
+└── src/core/memory/            │   ├── requirements-validation/
+    └── scattered impls         │   ├── code-intelligence/
+                                │   ├── security-compliance/
+                                │   ├── contract-testing/
+                                │   ├── visual-accessibility/
+                                │   ├── chaos-resilience/
+                                │   └── learning-optimization/
+                                ├── src/kernel/
+                                │   ├── event-bus.ts
+                                │   └── coordinator.ts
+                                └── src/mcp/
+                                    └── domain-handlers.ts
+```
+
+### Key API Changes
+
+| v2 API | v3 API | Notes |
+|--------|--------|-------|
+| `aqe init` | `aqe-v3 init` | Different binary |
+| `aqe.generateTests()` | `testGeneration.generate()` | Domain-based |
+| `aqe.analyzeGaps()` | `coverageAnalysis.findGaps()` | O(log n) now |
+| `memory.store()` | `agentDB.store()` | HNSW-indexed |
+| `patterns.learn()` | `reasoningBank.record()` | With verdicts |
+
+---
+
+## Configuration Migration
+
+### v2 Config Format
+```json
+{
+  "version": "2.8.2",
+  "memory": {
+    "path": ".agentic-qe/memory.db",
+    "type": "sqlite"
+  },
+  "agents": {
+    "enabled": ["test-generator", "coverage-analyzer"]
+  }
+}
+```
+
+### v3 Config Format
+```json
+{
+  "version": "3.0.0",
+  "kernel": {
+    "eventBus": "in-memory",
+    "coordinator": "queen"
+  },
+  "domains": {
+    "test-generation": { "enabled": true },
+    "test-execution": { "enabled": true },
+    "coverage-analysis": {
+      "enabled": true,
+      "algorithm": "hnsw",
+      "dimensions": 128
+    }
+  },
+  "memory": {
+    "backend": "agentdb",
+    "path": ".aqe-v3/agentdb/",
+    "hnsw": {
+      "M": 16,
+      "efConstruction": 200
+    }
+  },
+  "learning": {
+    "reasoningBank": true,
+    "sona": true
+  }
+}
+```
+
+---
+
+## Memory Migration
+
+### SQLite to AgentDB
+
+```typescript
+// v2: Direct SQLite access
+import Database from 'better-sqlite3';
+const db = new Database('.agentic-qe/memory.db');
+const patterns = db.prepare('SELECT * FROM patterns').all();
+
+// v3: AgentDB with HNSW
+import { AgentDB } from '@agentic-qe/v3';
+const db = new AgentDB('.aqe-v3/agentdb/');
+await db.initialize({ dimensions: 128, M: 16 });
+
+// Migration script transfers and indexes
+for (const pattern of v2Patterns) {
+  await db.store({
+    key: pattern.id,
+    value: pattern.data,
+    embedding: await generateEmbedding(pattern.data),
+    metadata: { migratedFrom: 'v2', originalId: pattern.id }
+  });
+}
+```
+
+---
+
+## Breaking Changes
+
+### Must Update
+
+1. **Import Paths**
+   ```typescript
+   // v2
+   import { AgenticQE } from 'agentic-qe';
+
+   // v3
+   import { TestGenerationDomain } from '@agentic-qe/v3/domains';
+   ```
+
+2. **CLI Commands**
+   ```bash
+   # v2
+   aqe test --parallel
+
+   # v3
+   aqe-v3 test --workers=4 --topology=mesh
+   ```
+
+3. **MCP Server**
+   ```bash
+   # v2
+   claude mcp add aqe -- npx aqe-mcp
+
+   # v3
+   claude mcp add aqe-v3 -- npx @agentic-qe/v3 mcp
+   ```
+
+### Deprecated (Will Warn)
+
+- `aqe.runTests()` → Use domain-specific methods
+- Direct memory access → Use AgentDB API
+- Flat agent list → Use domain coordinators
+
+---
+
+## Rollback Instructions
+
+If migration fails or you need to revert:
+
+```bash
+# 1. v3 does NOT modify v2 data
+# Your .agentic-qe/ folder is untouched
+
+# 2. Remove v3 installation
+npm uninstall @agentic-qe/v3
+rm -rf .aqe-v3/
+
+# 3. Continue using v2
+aqe --version  # Should show 2.x.x
+```
+
+---
+
+## Agent Coordination Examples
+
+### Spawning Migration Agents
+
+```typescript
+// Use Task tool to spawn migration agents in parallel
+Task({
+  prompt: "Analyze v2 memory.db and extract all patterns",
+  subagent_type: "researcher",
+  description: "Analyze v2 patterns"
+});
+
+Task({
+  prompt: "Convert v2 config to v3 format",
+  subagent_type: "coder",
+  description: "Convert config"
+});
+
+Task({
+  prompt: "Validate migration results",
+  subagent_type: "tester",
+  description: "Validate migration"
+});
+```
+
+---
+
+## Troubleshooting
+
+### Common Issues
+
+| Issue | Cause | Solution |
+|-------|-------|----------|
+| "Cannot find .agentic-qe/" | No v2 installation | Run `aqe init` first |
+| "Memory migration failed" | Corrupted SQLite | Use backup: `npm run backup:restore` |
+| "HNSW index error" | Dimension mismatch | Set `dimensions: 128` in config |
+| "Pattern not found" | Not migrated | Re-run: `aqe-v3 migrate --patterns` |
+
+### Debug Mode
+
+```bash
+# Run migration with debug output
+DEBUG=aqe:migrate npx aqe-v3 migrate
+
+# Check migration logs
+cat .aqe-v3/logs/migration.log
+```
+
+---
+
+## Support
+
+- **Migration Issues**: Open issue with `[v2-v3-migration]` tag
+- **Documentation**: [Migration Guide](../../docs/plans/V2-TO-V3-MIGRATION-PLAN.md)
+- **Discord**: #v3-migration channel
+
+---
+
+## Version Compatibility Matrix
+
+| v2 Version | v3 Version | Migration Support |
+|------------|------------|-------------------|
+| 2.8.x | 3.0.x | Full |
+| 2.7.x | 3.0.x | Full |
+| 2.6.x | 3.0.x | Partial (config only) |
+| 2.5.x and below | 3.0.x | Manual migration |
+
+---
+
+*Skill Version: 1.0.0 | Last Updated: 2026-01-11*

package/assets/skills/brutal-honesty-review/README.md

@@ -0,0 +1,218 @@
+# Brutal Honesty Review Skill
+
+## Overview
+
+A QE skill that delivers unvarnished technical criticism combining three legendary personas:
+- **Linus Torvalds**: Surgical technical precision
+- **Gordon Ramsay**: Standards-driven quality assessment
+- **James Bach**: BS detection in testing practices
+
+## Purpose
+
+Unlike diplomatic reviews, this skill eliminates ambiguity about technical standards. It **dissects why something is wrong, explains the correct approach, and has zero patience for repeated mistakes or sloppy thinking**.
+
+## When to Use
+
+✅ **Appropriate**:
+- Senior engineers wanting unfiltered feedback
+- Repeated architectural mistakes
+- Critical bugs requiring immediate attention
+- Evaluating vendor claims/certifications
+- Teams explicitly requesting no-BS feedback
+
+❌ **Inappropriate**:
+- Junior developers' first contributions
+- Demoralized teams
+- Public forums (avoid humiliation)
+- When psychological safety is low
+
+## Three Modes
+
+### 1. Linus Mode (Technical Precision)
+Focus on code correctness, performance, concurrency, and architecture.
+
+**Example**:
+> "This is completely broken. You're holding the lock during I/O, which means every thread serializes. Did you even test under load? The correct approach is..."
+
+### 2. Ramsay Mode (Standards-Driven Quality)
+Compare reality against clear excellence model using concrete metrics.
+
+**Example**:
+> "Look at this! 12 tests and 10 are just checking if variables exist. Where's the business logic coverage? This is RAW. Don't merge it."
+
+### 3. Bach Mode (BS Detection)
+Question certifications, best practices, and vendor hype.
+
+**Example**:
+> "This certification teaches scripts, not thinking. Does it help testers find bugs faster? No. It helps the cert body make money."
+
+## Quick Start
+
+### Using the Skill
+
+Invoke the skill when you need brutal honesty:
+
+```markdown
+Use brutal-honesty-review skill in Linus mode to review this code:
+[paste code]
+```
+
+### Using Assessment Scripts
+
+```bash
+# Assess code quality (Linus Mode)
+./scripts/assess-code.sh src/myfile.js
+
+# Assess test quality (Ramsay Mode)
+./scripts/assess-tests.sh tests/
+```
+
+## Files Included
+
+```
+brutal-honesty-review/
+├── SKILL.md                          # Main skill instructions
+├── README.md                         # This file
+├── resources/
+│   ├── review-template.md            # Template for structured reviews
+│   └── assessment-rubrics.md         # Scoring rubrics for all modes
+└── scripts/
+    ├── assess-code.sh                # Automated code quality check
+    └── assess-tests.sh               # Automated test quality check
+```
+
+## Assessment Rubrics
+
+### Code Quality (Linus Mode)
+
+| Criteria | Failing | Passing | Excellent |
+|----------|---------|---------|-----------|
+| Correctness | Wrong logic | Works in tested cases | Proven across edge cases |
+| Performance | O(n²) where O(n) exists | Acceptable | Optimal + profiled |
+| Error Handling | Crashes | Returns errors | Graceful degradation |
+| Concurrency | Race conditions | Thread-safe | Lock-free/proven |
+| Testability | Can't unit test | Mockable | Self-testing |
+| Maintainability | "Clever" code | Clear | Self-documenting |
+
+**Threshold**: Minimum "Passing" on ALL to merge.
+
+### Test Quality (Ramsay Mode)
+
+| Criteria | Raw | Acceptable | Michelin Star |
+|----------|-----|------------|---------------|
+| Coverage | <50% | 80%+ | 95%+ + mutation |
+| Edge Cases | Happy path only | Common failures | Boundary analysis |
+| Clarity | Unclear names | Clear names | Self-documenting |
+| Speed | Minutes | <10s | <1s, parallel |
+| Stability | Flaky (>1%) | Stable | Deterministic |
+| Isolation | Dependent | Independent | Pure, stateless |
+
+**Threshold**: Minimum "Acceptable" on ALL to merge.
+
+### BS Detection (Bach Mode)
+
+Red flags:
+- Cargo cult practices (no context)
+- Certification theater (filters thinkers)
+- Vendor lock-in (solves own problem)
+- False automation (still needs humans)
+- Checkbox quality (compliance, not outcomes)
+- Hype cycle (10x claims without proof)
+
+**Green flag test**: "Does this help testers/developers do better work in THIS context?"
+
+## Examples
+
+### Example 1: Linus Mode - Concurrency Bug
+
+**Problem**: Holding DB connection during HTTP call
+
+**Brutal Honesty**:
+> "This is completely broken. You're holding a database connection open while waiting for an HTTP request. Under load, you'll exhaust the connection pool in seconds. Did you test with >1 user? The correct approach: 1) Fetch data, 2) Close connection, 3) Make HTTP call."
+
+### Example 2: Ramsay Mode - Weak Tests
+
+**Problem**: 15 tests, all happy path
+
+**Brutal Honesty**:
+> "Look at this test suite. 15 tests, 14 are happy path. Where's validation? Where are edge cases? This is RAW. You're testing if code runs, not if it's correct. You have 35% coverage. Production needs 80%+. Don't merge this."
+
+### Example 3: Bach Mode - Certification Theater
+
+**Problem**: Required ISTQB certification
+
+**Brutal Honesty**:
+> "ISTQB tests if you memorized terminology, not if you can test software. Real skills: finding bugs, designing strategies, communicating risk. ISTQB tests: definitions, model names, checkbox thinking. If it helped, ISTQB-certified teams would ship higher quality. They don't."
+
+## Calibration Guide
+
+### Harshness Levels
+
+**Level 1 - Direct**: For experienced engineers
+> "This approach is flawed because..."
+
+**Level 2 - Harsh**: For repeated mistakes
+> "We've discussed this pattern three times. Why is it back?"
+
+**Level 3 - Brutal**: For critical issues or willful ignorance
+> "This is negligent. You're exposing user data because..."
+
+### Context Matters
+
+Before being brutal, verify:
+1. **Audience maturity**: Can they handle directness?
+2. **Relationship capital**: Have you earned harsh feedback rights?
+3. **Actionability**: Can they actually fix this?
+4. **Intent**: Helping or venting?
+
+## Philosophy
+
+### Why Brutal Honesty Works
+
+1. **Eliminates Ambiguity**: No confusion about technical standards
+2. **Scales Teaching**: Public technical breakdown teaches entire team
+3. **Cuts Through BS**: Exposes cargo cult practices and vendor hype
+
+### The Costs
+
+1. **Relationship Damage**: Harsh criticism without trust destroys collaboration
+2. **Chills Participation**: Fear stops newcomers from contributing
+3. **Burnout**: Constant harshness is exhausting
+
+### The Contract
+
+Before using brutal honesty, establish explicit contract:
+
+> "I'm going to give unfiltered technical feedback. This will be direct, possibly harsh. Goal is clarity, not cruelty. I'll explain: 1) What's wrong, 2) Why, 3) What correct looks like, 4) How to fix. Want diplomatic instead?"
+
+**Get explicit consent first.**
+
+## Integration with Agentic QE Fleet
+
+This skill extends the QE skill set:
+
+- **Complements**: `code-review-quality`, `context-driven-testing`
+- **Contrasts with**: Diplomatic, constructive review approaches
+- **Use when**: Technical precision and BS-cutting are priorities
+- **Avoid when**: Building confidence or psychological safety
+
+## Related Skills
+
+- `code-review-quality` - Diplomatic code review
+- `context-driven-testing` - Foundation for BS detection
+- `tdd-london-chicago` - Systematic quality approach
+- `exploratory-testing-advanced` - Critical thinking in testing
+
+## License
+
+MIT - Part of Agentic QE Fleet
+
+## Contributing
+
+Found this too harsh? Good. Found this too soft? You're Linus Torvalds.
+
+Submit issues if the skill produces ineffective criticism (not actionable, personal attacks, wrong context).
+
+---
+
+**Remember**: Brutal honesty is a tool, not a personality. Use it when it helps, not when it harms.