agentic-qe 1.6.0 → 1.6.1

package/.claude/skills/cicd-pipeline-qe-orchestrator/resources/workflows/monolith-pipeline.md

@@ -0,0 +1,268 @@
+# Monolith CI/CD Pipeline Workflow
+
+Complete quality orchestration workflow for monolithic applications.
+
+## Pipeline Configuration
+
+**Service Type**: Monolithic Web Application
+**Tech Stack**: Full-stack (Frontend + Backend)
+**Deployment**: Traditional servers, VM-based
+**Frequency**: Weekly releases
+
+---
+
+## Phase 1: Commit (Pre-Merge)
+
+### Quality Strategy
+- Fast feedback on changed modules
+- Component-level testing
+- Risk-based test selection
+
+### Agent Orchestration
+
+```javascript
+// Smart test selection for large codebase
+Task("Risk Analysis", "Identify affected modules and tests", "qe-regression-risk-analyzer")
+Task("Targeted Tests", "Run minimal test suite based on changes", "qe-test-executor")
+Task("Flaky Detection", "Check for flaky tests in suite", "qe-flaky-test-hunter")
+```
+
+### Quality Gates
+- [ ] Affected modules tested (100% coverage)
+- [ ] No flaky tests in selection
+- [ ] No breaking changes to public APIs
+- [ ] Execution time < 10 minutes
+
+---
+
+## Phase 2: Build (Full Suite)
+
+### Quality Strategy
+- Comprehensive regression testing
+- Full coverage analysis
+- Mutation testing for critical paths
+
+### Agent Orchestration
+
+```javascript
+// Full regression suite (batched execution)
+Task("Full Regression", "Run complete test suite in batches", "qe-test-executor")
+Task("Coverage Analysis", "Analyze coverage across all modules", "qe-coverage-analyzer")
+Task("Mutation Testing", "Validate test quality on critical code", "qe-test-executor")
+```
+
+### Quality Gates
+- [ ] All 1000+ tests passing
+- [ ] Coverage > 85% overall
+- [ ] Coverage > 95% on critical paths
+- [ ] Mutation score > 75%
+
+---
+
+## Phase 3: Integration / Test Environment
+
+### Quality Strategy
+- Database migration testing
+- Performance baseline validation
+- Security compliance scanning
+- Accessibility validation
+
+### Agent Orchestration
+
+```javascript
+// Comprehensive validation
+Task("DB Migration", "Validate database schema changes", "qe-test-executor")
+Task("Performance Baseline", "Establish performance benchmarks", "qe-performance-tester")
+Task("Security Compliance", "OWASP Top 10 + compliance checks", "qe-security-scanner")
+Task("Accessibility", "WCAG 2.2 validation", "qe-visual-tester")
+```
+
+### Quality Gates
+- [ ] Database migrations successful
+- [ ] Performance within 10% of baseline
+- [ ] No critical/high security vulnerabilities
+- [ ] WCAG AA compliance achieved
+
+---
+
+## Phase 4: UAT / Staging
+
+### Quality Strategy
+- Exploratory testing sessions
+- Visual regression across browsers
+- Mobile compatibility
+- User acceptance criteria validation
+
+### Agent Orchestration
+
+```javascript
+// User acceptance and compatibility
+Task("Visual Regression", "Test across Chrome, Firefox, Safari, Edge", "qe-visual-tester")
+Task("Mobile Testing", "iOS and Android compatibility", "qe-visual-tester")
+Task("Deployment Readiness", "Pre-production assessment", "qe-deployment-readiness")
+```
+
+### Skills for Manual Testing
+```javascript
+// Invoke skills for exploratory testing guidance
+Skill("exploratory-testing-advanced")  // SBTM session planning
+Skill("context-driven-testing")        // Adapt testing to context
+```
+
+### Quality Gates
+- [ ] Visual tests passing (4 browsers)
+- [ ] Mobile responsive (iOS/Android)
+- [ ] UAT sign-off received
+- [ ] Deployment checklist complete
+
+---
+
+## Phase 5: Production
+
+### Quality Strategy
+- Blue-green deployment
+- Smoke tests in production
+- Compliance validation
+- Production monitoring
+
+### Agent Orchestration
+
+```javascript
+// Production validation
+Task("Smoke Tests", "Run critical path smoke tests", "qe-test-executor")
+Task("Compliance Check", "GDPR, HIPAA, SOC2 validation", "qe-quality-gate")
+Task("Production Intelligence", "Monitor first hour metrics", "qe-production-intelligence")
+```
+
+### Quality Gates
+- [ ] All smoke tests passing
+- [ ] Compliance checks passed
+- [ ] Error rate < 0.5%
+- [ ] No user-reported critical bugs (first 24h)
+
+---
+
+## Skill Integration
+
+### Skills Used by Phase
+
+**Commit Phase**:
+- `shift-left-testing`
+- `risk-based-testing`
+- `regression-testing`
+
+**Build Phase**:
+- `test-automation-strategy`
+- `mutation-testing`
+- `refactoring-patterns`
+
+**Integration Phase**:
+- `database-testing`
+- `performance-testing`
+- `security-testing`
+- `accessibility-testing`
+
+**UAT/Staging Phase**:
+- `exploratory-testing-advanced`
+- `context-driven-testing`
+- `compatibility-testing`
+- `visual-testing-advanced`
+
+**Production Phase**:
+- `shift-right-testing`
+- `compliance-testing`
+- `quality-metrics`
+
+---
+
+## Complete Pipeline Code
+
+```javascript
+// Full monolith pipeline orchestration
+
+// PHASE 1: Commit (Smart Selection)
+Task("Risk Analysis", "Select minimal test suite for changes", "qe-regression-risk-analyzer")
+Task("Targeted Testing", "Run selected tests", "qe-test-executor")
+
+// PHASE 2: Build (Full Suite)
+Task("Full Regression", "Run all 1000+ tests in batches", "qe-test-executor")
+Task("Coverage Analysis", "Analyze full coverage", "qe-coverage-analyzer")
+Task("Mutation Testing", "Test quality validation", "qe-test-executor")
+
+// PHASE 3: Integration
+Task("DB Migrations", "Validate schema changes", "qe-test-executor")
+Task("Performance Test", "Baseline performance validation", "qe-performance-tester")
+Task("Security Scan", "OWASP + compliance scanning", "qe-security-scanner")
+Task("Accessibility", "WCAG 2.2 validation", "qe-visual-tester")
+
+// PHASE 4: UAT/Staging
+Task("Visual Regression", "Cross-browser testing", "qe-visual-tester")
+Task("Mobile Testing", "iOS/Android compatibility", "qe-visual-tester")
+Task("Readiness Check", "Deployment assessment", "qe-deployment-readiness")
+
+// Manual testing with skill guidance
+Skill("exploratory-testing-advanced")
+
+// PHASE 5: Production
+Task("Smoke Tests", "Critical path validation", "qe-test-executor")
+Task("Compliance", "Regulatory validation", "qe-quality-gate")
+Task("Monitoring", "Production intelligence", "qe-production-intelligence")
+```
+
+---
+
+## Timing Budget
+
+| Phase | Target Time | Max Time |
+|-------|-------------|----------|
+| Commit | 8 min | 15 min |
+| Build | 45 min | 90 min |
+| Integration | 60 min | 120 min |
+| UAT/Staging | 4 hours (+ manual) | 8 hours |
+| Production Deploy | 30 min | 60 min |
+| **Total** | **~6 hours** | **~12 hours** |
+
+---
+
+## Weekly Release Schedule
+
+**Monday**: Freeze features, start testing
+**Tuesday-Wednesday**: Integration + UAT
+**Thursday**: Staging validation
+**Friday**: Production deployment (morning)
+**Weekend**: Monitor production
+
+---
+
+## Database Migration Strategy
+
+### Pre-Deploy Validation
+
+```javascript
+// Validate migrations before deployment
+Task("Schema Validation", "Check migrations are reversible", "qe-test-executor")
+Task("Data Integrity", "Validate data after migration", "qe-test-executor")
+```
+
+### Post-Deploy Verification
+
+```javascript
+// Verify migrations in production
+Task("Production Validation", "Check schema and data integrity", "qe-production-intelligence")
+```
+
+---
+
+## Rollback Strategy
+
+**Build Failure**: Fix and rebuild
+**Integration Failure**: Investigate, may delay release
+**UAT Failure**: Block release, fix critical issues
+**Production Issues**: Blue-green rollback, investigate
+
+---
+
+**Use Cases**: E-commerce, CMS, Enterprise web apps
+**Team Size**: 10-50 developers
+**Deploy Frequency**: Weekly releases
+**Database**: PostgreSQL, MySQL with migrations

package/.claude/skills/six-thinking-hats/README.md

@@ -0,0 +1,190 @@
+# Six Thinking Hats for Testing
+
+A comprehensive Claude Code skill that applies Edward de Bono's Six Thinking Hats methodology to software testing contexts.
+
+## Quick Overview
+
+**What It Does**: Enables structured exploration of quality concerns from six distinct perspectives (facts, emotions, risks, benefits, creativity, and process) to uncover blind spots and make better testing decisions.
+
+**When to Use**:
+- Designing test strategies for new features
+- Conducting test retrospectives
+- Analyzing test failures or production incidents
+- Evaluating testing approaches
+- Facilitating testing discussions with teams
+- Overcoming analysis paralysis in testing decisions
+
+## The Six Hats
+
+| Hat | Focus | Testing Application | Time |
+|-----|-------|---------------------|------|
+| 🤍 **White** | Facts & Data | Test metrics, coverage, defect data | 5 min |
+| ❤️ **Red** | Feelings & Intuition | Gut instincts about quality, confidence | 3 min |
+| 🖤 **Black** | Risks & Problems | What could go wrong, coverage gaps | 7 min |
+| 💛 **Yellow** | Benefits & Opportunities | Testing strengths, quick wins | 5 min |
+| 💚 **Green** | Creativity & Alternatives | Innovative test approaches | 7 min |
+| 🔵 **Blue** | Process & Organization | Test strategy, action plan | 5 min |
+
+**Total**: 30 minutes for solo session, 60-90 minutes for team session
+
+## Quick Start
+
+### Solo Session (30 minutes)
+
+```bash
+# 1. Copy the template
+cp .claude/skills/six-thinking-hats/resources/templates/solo-session-template.md my-analysis.md
+
+# 2. Define your testing focus
+# Example: "Test strategy for user authentication feature"
+
+# 3. Work through each hat sequentially (use timer!)
+# White Hat (5 min): List facts, metrics, data
+# Red Hat (3 min): Capture gut feelings, no justification
+# Black Hat (7 min): Identify risks, gaps, problems
+# Yellow Hat (5 min): Find strengths, opportunities
+# Green Hat (7 min): Generate creative testing ideas
+# Blue Hat (5 min): Create action plan
+
+# 4. Synthesize into actionable test plan
+```
+
+### Team Session (90 minutes)
+
+```bash
+# 1. Copy the team template
+cp .claude/skills/six-thinking-hats/resources/templates/team-session-template.md team-session.md
+
+# 2. Pre-session: Gather data (White Hat prep)
+
+# 3. Run session with strict time boundaries
+# - Blue Hat opening: 5 min (set context)
+# - White Hat: 10 min (collect facts round-robin)
+# - Red Hat: 5 min (silent reflection + sharing)
+# - Black Hat: 12 min (brainstorm risks)
+# - Yellow Hat: 8 min (identify opportunities)
+# - Green Hat: 15 min (rapid ideation)
+# - Blue Hat: 10 min (synthesize action plan)
+
+# 4. Post-session: Document and share (20 min)
+```
+
+## File Structure
+
+```
+.claude/skills/six-thinking-hats/
+├── SKILL.md                           # Main skill documentation
+├── README.md                          # This file (human-readable overview)
+├── resources/
+│   ├── templates/
+│   │   ├── solo-session-template.md  # Template for individual use
+│   │   └── team-session-template.md  # Template for team sessions
+│   └── examples/
+│       └── api-testing-example.md    # Complete worked example
+```
+
+## When to Use Which Format
+
+### Solo Session (30 min)
+✅ **Use when**:
+- Quick decision needed
+- Individual test analysis
+- Personal exploration
+- Preparing for team discussion
+
+### Team Session (90 min)
+✅ **Use when**:
+- Complex testing challenges
+- Cross-functional alignment needed
+- Multiple perspectives valuable
+- Shared understanding required
+
+### Async Session (2-3 days)
+✅ **Use when**:
+- Distributed team
+- Deep thinking needed
+- Time zone challenges
+- Written documentation desired
+
+## Integration with Other QE Skills
+
+Works exceptionally well with:
+- `context-driven-testing` - Choose practices based on context
+- `risk-based-testing` - Prioritize using Black Hat
+- `exploratory-testing-advanced` - Use Green Hat for creative charters
+- `holistic-testing-pact` - Comprehensive quality model (all hats)
+
+## Key Benefits
+
+1. **Uncovers Blind Spots**: Each hat reveals different insights
+2. **Balances Perspectives**: Black Hat pessimism balanced by Yellow Hat optimism
+3. **Structures Discussion**: Prevents chaotic brainstorming
+4. **Builds Consensus**: Team alignment through shared process
+5. **Saves Time**: 30-90 min investment prevents days of rework
+6. **Validates Intuition**: Red Hat legitimizes gut feelings
+7. **Drives Creativity**: Green Hat forces innovative thinking
+
+## Common Pitfalls to Avoid
+
+❌ **Hat Mixing**: Combining perspectives (e.g., "Tests are passing (White) but I'm worried (Red)")
+- ✅ **Solution**: Strict separation, use timer
+
+❌ **Justifying Red Hat**: Rationalizing feelings instead of trusting intuition
+- ✅ **Solution**: "I feel X" not "I feel X because..."
+
+❌ **Skipping Hats**: "We don't need Green Hat"
+- ✅ **Solution**: Every hat reveals insights, wear all six
+
+❌ **Rushing**: 5 minutes for all hats
+- ✅ **Solution**: Minimum 5 min per hat, use timer
+
+❌ **Judging Contributions**: Criticizing ideas during Green Hat
+- ✅ **Solution**: All ideas valid, evaluate later in Blue Hat
+
+## Success Metrics
+
+A successful Six Hats session should produce:
+- ✅ 10+ facts documented (White Hat)
+- ✅ Honest feelings captured (Red Hat)
+- ✅ 5+ risks identified (Black Hat)
+- ✅ 3+ opportunities found (Yellow Hat)
+- ✅ 5+ creative ideas generated (Green Hat)
+- ✅ Clear action plan with owners (Blue Hat)
+
+## Resources
+
+### Templates
+- `resources/templates/solo-session-template.md` - Individual analysis
+- `resources/templates/team-session-template.md` - Team facilitation
+
+### Examples
+- `resources/examples/api-testing-example.md` - Complete worked example with real test strategy
+
+### Further Reading
+- **SKILL.md** - Complete documentation with all use cases
+- **"Six Thinking Hats" by Edward de Bono** - Original methodology
+- **"Context-Driven Testing"** - Related testing philosophy
+
+## Quick Tips
+
+1. **Use Timer**: Strict time boundaries improve quality
+2. **Start with Black Hat**: Teams love identifying risks
+3. **Trust Red Hat**: Intuition catches what analysis misses
+4. **Go Wild in Green Hat**: No idea too crazy
+5. **Close with Blue Hat**: Always end with action plan
+6. **Document Everything**: Especially Green Hat wild ideas
+7. **Practice Solo First**: Get comfortable before facilitating teams
+
+## Support
+
+- Main documentation: `SKILL.md`
+- Templates: `resources/templates/`
+- Examples: `resources/examples/`
+- Related skills: `context-driven-testing`, `risk-based-testing`, `exploratory-testing-advanced`
+
+---
+
+**Created**: 2025-11-13
+**Category**: Testing Methodologies
+**Difficulty**: Intermediate
+**Best Used With**: context-driven-testing, risk-based-testing, exploratory-testing-advanced