agentic-qe 3.8.0 → 3.8.2

package/.opencode/skills/qe-security-testing.yaml

@@ -0,0 +1,45 @@
+name: qe-security-testing
+description: "Test for security vulnerabilities using OWASP principles. Use when conducting security audits, testing auth, or implementing security practices."
+minModelTier: tier3-best
+tags: ["security", "owasp", "sast", "dast", "vulnerabilities", "auth", "injection", "qe", "quality-engineering", "specialized-testing"]
+steps:
+  - name: owasp-top-10-2021
+    description: "OWASP Top 10 (2021)"
+    tools: ["bash", "read"]
+    prompt: |
+      OWASP Top 10 (2021)
+  - name: key-vulnerability-tests
+    description: "Key Vulnerability Tests"
+    tools: ["bash", "read"]
+    prompt: |
+      Key Vulnerability Tests
+  - name: 1-broken-access-control
+    description: "1. Broken Access Control"
+    tools: ["bash", "read"]
+    prompt: |
+      1. Broken Access Control
+  - name: 2-injection-attacks
+    description: "2. Injection Attacks"
+    tools: ["bash", "read", "grep"]
+    prompt: |
+      2. Injection Attacks
+  - name: 3-cryptographic-failures
+    description: "3. Cryptographic Failures"
+    tools: ["bash", "read", "grep"]
+    prompt: |
+      3. Cryptographic Failures
+  - name: 4-security-misconfiguration
+    description: "4. Security Misconfiguration"
+    tools: ["bash", "read"]
+    prompt: |
+      4. Security Misconfiguration
+  - name: 5-rate-limiting
+    description: "5. Rate Limiting"
+    tools: ["bash", "read"]
+    prompt: |
+      5. Rate Limiting
+  - name: security-checklist
+    description: "Security Checklist"
+    tools: ["bash", "read"]
+    prompt: |
+      Security Checklist

package/.opencode/skills/qe-security-visual-testing.yaml

@@ -0,0 +1,45 @@
+name: qe-security-visual-testing
+description: "Security-first visual testing combining URL validation, PII detection, and visual regression with parallel viewport support. Use when testing web applications that handle sensitive data, need visual regression coverage, or require WCAG accessibility compliance."
+minModelTier: tier3-best
+tags: ["security", "visual-testing", "pii", "accessibility", "wcag", "parallel-viewport", "regression", "qe", "quality-engineering", "specialized-testing"]
+steps:
+  - name: key-capabilities
+    description: "Key Capabilities"
+    tools: ["bash", "read", "grep"]
+    prompt: |
+      Key Capabilities
+  - name: workflows
+    description: "Workflows"
+    tools: ["bash", "read"]
+    prompt: |
+      Workflows
+  - name: 1-security-visual-audit-full-pipeline
+    description: "1. Security Visual Audit (Full Pipeline)"
+    tools: ["bash", "read"]
+    prompt: |
+      1. Security Visual Audit (Full Pipeline)
+  - name: 2-pii-safe-screenshot
+    description: "2. PII-Safe Screenshot"
+    tools: ["bash", "read", "edit"]
+    prompt: |
+      2. PII-Safe Screenshot
+  - name: 3-responsive-visual-audit
+    description: "3. Responsive Visual Audit"
+    tools: ["bash", "read"]
+    prompt: |
+      3. Responsive Visual Audit
+  - name: integration-with-aqe-v3
+    description: "Integration with AQE v3"
+    tools: ["bash", "read"]
+    prompt: |
+      Integration with AQE v3
+  - name: using-with-browsersecurityscanner
+    description: "Using with BrowserSecurityScanner"
+    tools: ["bash", "read", "mcp:agentic-qe:*"]
+    prompt: |
+      Using with BrowserSecurityScanner
+  - name: using-with-trajectoryadapter
+    description: "Using with TrajectoryAdapter"
+    tools: ["bash", "read", "mcp:agentic-qe:*"]
+    prompt: |
+      Using with TrajectoryAdapter

package/.opencode/skills/qe-sfdipot-product-factors.yaml

@@ -0,0 +1,45 @@
+name: qe-sfdipot-product-factors
+description: "James Bach's HTSM Product Factors (SFDIPOT) analysis for comprehensive test strategy generation. Use when analyzing requirements, epics, or user stories to generate prioritized test ideas across Structure, Function, Data, Interfaces, Platform, Operations, and Time dimensions."
+minModelTier: tier2-good
+tags: ["sfdipot", "htsm", "product-factors", "test-strategy", "requirements", "james-bach", "qe", "quality-engineering", "requirements-analysis"]
+steps:
+  - name: the-7-product-factors
+    description: "The 7 Product Factors"
+    tools: ["bash", "read"]
+    prompt: |
+      The 7 Product Factors
+  - name: sfdipot-analysis-framework
+    description: "SFDIPOT Analysis Framework"
+    tools: ["bash", "read"]
+    prompt: |
+      SFDIPOT Analysis Framework
+  - name: structure-what-the-product-is
+    description: "**Subcategories:** - Code Integrity: Code quality, complexity, maintainability - Hardware: Physical components, devices, peripherals - Non-Executable Files: Config, data files, documents - Executable Files: Binaries, scripts, libraries - Dependencies: Third-party libraries, external services"
+    tools: ["bash", "read", "edit"]
+    prompt: |
+      **Subcategories:** - Code Integrity: Code quality, complexity, maintainability - Hardware: Physical components, devices, peripherals - Non-Executable Files: Config, data files, documents - Executable Files: Binaries, scripts, libraries - Dependencies: Third-party libraries, external services
+  - name: function-what-the-product-does
+    description: "**Subcategories:** - Application: Core business features - Calculation: Mathematical operations, transformations - Error Handling: Exception management, recovery - Security: Authentication, authorization, encryption - State Transitions: Workflow states, data lifecycle - Messaging: Notifications, eve"
+    tools: ["bash", "read", "grep"]
+    prompt: |
+      **Subcategories:** - Application: Core business features - Calculation: Mathematical operations, transformations - Error Handling: Exception management, recovery - Security: Authentication, authorization, encryption - State Transitions: Workflow states, data lifecycle - Messaging: Notifications, eve
+  - name: data-what-the-product-processes
+    description: "**Subcategories:** - Input: User input, file uploads, API payloads - Output: Responses, reports, exports - Persistence: Database storage, caching - Storage: File systems, cloud storage - Boundaries: Min/max values, edge cases - Validation: Format rules, business rules - Formats: JSON, XML, CSV handl"
+    tools: ["bash", "read"]
+    prompt: |
+      **Subcategories:** - Input: User input, file uploads, API payloads - Output: Responses, reports, exports - Persistence: Database storage, caching - Storage: File systems, cloud storage - Boundaries: Min/max values, edge cases - Validation: Format rules, business rules - Formats: JSON, XML, CSV handl
+  - name: interfaces-how-the-product-connects
+    description: "**Subcategories:** - User Interface: Web, mobile, desktop UI - APIs: REST, GraphQL, gRPC endpoints - Integrations: Third-party service connections - Protocols: HTTP, WebSocket, MQTT - CLI: Command-line interfaces"
+    tools: ["bash", "read"]
+    prompt: |
+      **Subcategories:** - User Interface: Web, mobile, desktop UI - APIs: REST, GraphQL, gRPC endpoints - Integrations: Third-party service connections - Protocols: HTTP, WebSocket, MQTT - CLI: Command-line interfaces
+  - name: platform-what-the-product-depends-on
+    description: "**Subcategories:** - Browser: Chrome, Firefox, Safari, Edge - OS: Windows, macOS, Linux, iOS, Android - Hardware: CPU, memory, storage constraints - External Software: Databases, message queues - Network: Latency, bandwidth, offline"
+    tools: ["bash", "read", "mcp:agentic-qe:*"]
+    prompt: |
+      **Subcategories:** - Browser: Chrome, Firefox, Safari, Edge - OS: Windows, macOS, Linux, iOS, Android - Hardware: CPU, memory, storage constraints - External Software: Databases, message queues - Network: Latency, bandwidth, offline
+  - name: operations-how-the-product-is-used
+    description: "**Subcategories:** - Common Use: Happy path workflows - Extreme Use: Edge cases, stress conditions - User Management: Roles, permissions, profiles - Admin Operations: Configuration, monitoring - Recovery: Backup, restore, disaster recovery"
+    tools: ["bash", "read"]
+    prompt: |
+      **Subcategories:** - Common Use: Happy path workflows - Extreme Use: Edge cases, stress conditions - User Management: Roles, permissions, profiles - Admin Operations: Configuration, monitoring - Recovery: Backup, restore, disaster recovery

package/.opencode/skills/qe-sherlock-review.yaml

@@ -0,0 +1,45 @@
+name: qe-sherlock-review
+description: "Evidence-based investigative code review using deductive reasoning to determine what actually happened versus what was claimed. Use when verifying implementation claims, investigating bugs, validating fixes, or conducting root cause analysis. Elementary approach to finding truth through systematic o"
+minModelTier: tier2-good
+tags: ["investigation", "evidence-based", "code-review", "root-cause", "deduction", "qe", "quality-engineering", "quality-review"]
+steps:
+  - name: evidence-collection-checklist
+    description: "Evidence Collection Checklist"
+    tools: ["bash", "read", "edit"]
+    prompt: |
+      Evidence Collection Checklist
+  - name: verdict-levels
+    description: "Verdict Levels"
+    tools: ["bash", "read"]
+    prompt: |
+      Verdict Levels
+  - name: investigation-template
+    description: "Investigation Template"
+    tools: ["bash", "read"]
+    prompt: |
+      Investigation Template
+  - name: sherlock-investigation-claim
+    description: "Sherlock Investigation: [Claim]"
+    tools: ["bash", "read"]
+    prompt: |
+      Sherlock Investigation: [Claim]
+  - name: the-claim
+    description: "\"[What PR/commit claims to do]\""
+    tools: ["bash", "read"]
+    prompt: |
+      "[What PR/commit claims to do]"
+  - name: evidence-examined
+    description: "- Code changes: [files, lines] - Tests added: [count, coverage] - Behavior observed: [what actually happens]"
+    tools: ["bash", "read", "edit"]
+    prompt: |
+      - Code changes: [files, lines] - Tests added: [count, coverage] - Behavior observed: [what actually happens]
+  - name: deductive-analysis
+    description: "**Claim**: [specific assertion] **Evidence**: [what you found] **Deduction**: [logical conclusion] **Verdict**: ✓/⚠/✗"
+    tools: ["bash", "read"]
+    prompt: |
+      **Claim**: [specific assertion] **Evidence**: [what you found] **Deduction**: [logical conclusion] **Verdict**: ✓/⚠/✗
+  - name: findings
+    description: "- What works: [with evidence] - What doesn't: [with evidence] - What's missing: [gaps in implementation/testing]"
+    tools: ["bash", "read", "grep"]
+    prompt: |
+      - What works: [with evidence] - What doesn't: [with evidence] - What's missing: [gaps in implementation/testing]

package/.opencode/skills/qe-shift-left-testing.yaml

@@ -0,0 +1,45 @@
+name: qe-shift-left-testing
+description: "Move testing activities earlier in the development lifecycle to catch defects when they're cheapest to fix. Use when implementing TDD, CI/CD, or early quality practices."
+minModelTier: tier3-best
+tags: ["shift-left", "early-testing", "tdd", "bdd", "ci-cd", "prevention", "qe", "quality-engineering", "testing-methodologies"]
+steps:
+  - name: cost-of-defects-by-phase
+    description: "Cost of Defects by Phase"
+    tools: ["bash", "read", "edit"]
+    prompt: |
+      Cost of Defects by Phase
+  - name: test-pyramid
+    description: "Test Pyramid"
+    tools: ["bash", "read"]
+    prompt: |
+      Test Pyramid
+  - name: shift-left-levels
+    description: "Shift-Left Levels"
+    tools: ["bash", "read"]
+    prompt: |
+      Shift-Left Levels
+  - name: level-1-tests-in-every-pr
+    description: "Level 1: Tests in Every PR"
+    tools: ["bash", "read"]
+    prompt: |
+      Level 1: Tests in Every PR
+  - name: level-2-tdd-practice
+    description: "Level 2: TDD Practice"
+    tools: ["bash", "read"]
+    prompt: |
+      Level 2: TDD Practice
+  - name: level-3-bdd-in-refinement
+    description: "Level 3: BDD in Refinement"
+    tools: ["bash", "read"]
+    prompt: |
+      Level 3: BDD in Refinement
+  - name: level-4-risk-analysis-in-design
+    description: "Level 4: Risk Analysis in Design"
+    tools: ["bash", "read", "edit"]
+    prompt: |
+      Level 4: Risk Analysis in Design
+  - name: agent-assisted-shift-left
+    description: "Agent-Assisted Shift-Left"
+    tools: ["bash", "read", "edit"]
+    prompt: |
+      Agent-Assisted Shift-Left

package/.opencode/skills/qe-shift-right-testing.yaml

@@ -0,0 +1,45 @@
+name: qe-shift-right-testing
+description: "Testing in production with feature flags, canary deployments, synthetic monitoring, and chaos engineering. Use when implementing production observability or progressive delivery."
+minModelTier: tier3-best
+tags: ["shift-right", "production-testing", "canary", "feature-flags", "chaos-engineering", "monitoring", "qe", "quality-engineering", "testing-methodologies"]
+steps:
+  - name: shift-right-techniques
+    description: "Shift-Right Techniques"
+    tools: ["bash", "read"]
+    prompt: |
+      Shift-Right Techniques
+  - name: progressive-rollout-pattern
+    description: "Progressive Rollout Pattern"
+    tools: ["bash", "read"]
+    prompt: |
+      Progressive Rollout Pattern
+  - name: key-metrics-to-monitor
+    description: "Key Metrics to Monitor"
+    tools: ["bash", "read"]
+    prompt: |
+      Key Metrics to Monitor
+  - name: feature-flags
+    description: "Feature Flags"
+    tools: ["bash", "read"]
+    prompt: |
+      Feature Flags
+  - name: canary-deployment
+    description: "Canary Deployment"
+    tools: ["bash", "read"]
+    prompt: |
+      Canary Deployment
+  - name: synthetic-monitoring
+    description: "Synthetic Monitoring"
+    tools: ["bash", "read"]
+    prompt: |
+      Synthetic Monitoring
+  - name: chaos-engineering
+    description: "Chaos Engineering"
+    tools: ["bash", "read"]
+    prompt: |
+      Chaos Engineering
+  - name: production-pre-production-feedback-loop
+    description: "Production → Pre-Production Feedback Loop"
+    tools: ["bash", "read"]
+    prompt: |
+      Production → Pre-Production Feedback Loop

package/.opencode/skills/qe-six-thinking-hats.yaml

@@ -0,0 +1,45 @@
+name: qe-six-thinking-hats
+description: "Apply Edward de Bono's Six Thinking Hats methodology to software testing for comprehensive quality analysis. Use when designing test strategies, conducting test retrospectives, analyzing test failures, evaluating testing approaches, or facilitating testing discussions. Each hat provides a distinct t"
+minModelTier: tier1-any
+tags: ["thinking", "methodology", "decision-making", "collaboration", "analysis", "qe", "quality-engineering"]
+steps:
+  - name: the-six-hats
+    description: "The Six Hats"
+    tools: ["bash", "read"]
+    prompt: |
+      The Six Hats
+  - name: hat-details
+    description: "Hat Details"
+    tools: ["bash", "read"]
+    prompt: |
+      Hat Details
+  - name: -white-hat---facts-data
+    description: "**Output: Quantitative testing baseline**"
+    tools: ["bash", "read"]
+    prompt: |
+      **Output: Quantitative testing baseline**
+  - name: -black-hat---risks-cautions
+    description: "**Output: Comprehensive risk assessment**"
+    tools: ["bash", "read"]
+    prompt: |
+      **Output: Comprehensive risk assessment**
+  - name: -yellow-hat---benefits-optimism
+    description: "**Output: Strengths and opportunities**"
+    tools: ["bash", "read"]
+    prompt: |
+      **Output: Strengths and opportunities**
+  - name: -green-hat---creativity
+    description: "**Output: Innovative testing ideas**"
+    tools: ["bash", "read"]
+    prompt: |
+      **Output: Innovative testing ideas**
+  - name: -red-hat---emotions
+    description: "**Output: Team gut feelings (NO justification needed)**"
+    tools: ["bash", "read"]
+    prompt: |
+      **Output: Team gut feelings (NO justification needed)**
+  - name: -blue-hat---process
+    description: "**Output: Action plan with owners and timelines**"
+    tools: ["bash", "read"]
+    prompt: |
+      **Output: Action plan with owners and timelines**

package/.opencode/skills/qe-skill-builder.yaml

@@ -0,0 +1,45 @@
+name: qe-skill-builder
+description: "Create new Claude Code Skills with proper YAML frontmatter, progressive disclosure structure, and complete directory organization. Use when you need to build custom skills for specific workflows, generate skill templates, or understand the Claude Skills specification."
+minModelTier: tier2-good
+tags: ["qe", "quality-engineering"]
+steps:
+  - name: what-this-skill-does
+    description: "Creates production-ready Claude Code Skills with proper YAML frontmatter, progressive disclosure architecture, and complete file/folder structure. This skill guides you through building skills that Claude can autonomously discover and use across all surfaces (Claude.ai, Claude Code, SDK, API)."
+    tools: ["bash", "read"]
+    prompt: |
+      Creates production-ready Claude Code Skills with proper YAML frontmatter, progressive disclosure architecture, and complete file/folder structure. This skill guides you through building skills that Claude can autonomously discover and use across all surfaces (Claude.ai, Claude Code, SDK, API).
+  - name: creating-your-first-skill
+    description: "Creating Your First Skill"
+    tools: ["bash", "read"]
+    prompt: |
+      Creating Your First Skill
+  - name: what-this-skill-does
+    description: "[Your instructions here]"
+    tools: ["bash", "read"]
+    prompt: |
+      [Your instructions here]
+  - name: complete-specification
+    description: "Complete Specification"
+    tools: ["bash", "read"]
+    prompt: |
+      Complete Specification
+  - name: -yaml-frontmatter-required
+    description: "Every SKILL.md **must** start with YAML frontmatter containing exactly two required fields:"
+    tools: ["bash", "read"]
+    prompt: |
+      Every SKILL.md **must** start with YAML frontmatter containing exactly two required fields:
+  - name: -directory-structure
+    description: "📂 Directory Structure"
+    tools: ["bash", "read"]
+    prompt: |
+      📂 Directory Structure
+  - name: -progressive-disclosure-architecture
+    description: "Claude Code uses a **3-level progressive disclosure system** to scale to 100+ skills without context penalty:"
+    tools: ["bash", "read"]
+    prompt: |
+      Claude Code uses a **3-level progressive disclosure system** to scale to 100+ skills without context penalty:
+  - name: what-this-skill-does
+    description: "[Main instructions - loaded only when skill is active]"
+    tools: ["bash", "read"]
+    prompt: |
+      [Main instructions - loaded only when skill is active]

package/.opencode/skills/qe-sparc-methodology.yaml

@@ -0,0 +1,45 @@
+name: qe-sparc-methodology
+description: "SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration"
+minModelTier: tier2-good
+tags: ["qe", "quality-engineering", "development"]
+steps:
+  - name: overview
+    description: "SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) is a systematic development methodology integrated with Claude Flow's multi-agent orchestration capabilities. It provides 17 specialized modes for comprehensive software development, from initial research through deployment and "
+    tools: ["bash", "read", "grep"]
+    prompt: |
+      SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) is a systematic development methodology integrated with Claude Flow's multi-agent orchestration capabilities. It provides 17 specialized modes for comprehensive software development, from initial research through deployment and 
+  - name: table-of-contents
+    description: "1. [Core Philosophy](#core-philosophy) 2. [Development Phases](#development-phases) 3. [Available Modes](#available-modes) 4. [Activation Methods](#activation-methods) 5. [Orchestration Patterns](#orchestration-patterns) 6. [TDD Workflows](#tdd-workflows) 7. [Best Practices](#best-practices) 8. [Int"
+    tools: ["bash", "read"]
+    prompt: |
+      1. [Core Philosophy](#core-philosophy) 2. [Development Phases](#development-phases) 3. [Available Modes](#available-modes) 4. [Activation Methods](#activation-methods) 5. [Orchestration Patterns](#orchestration-patterns) 6. [TDD Workflows](#tdd-workflows) 7. [Best Practices](#best-practices) 8. [Int
+  - name: core-philosophy
+    description: "SPARC methodology emphasizes:"
+    tools: ["bash", "read", "mcp:agentic-qe:*"]
+    prompt: |
+      SPARC methodology emphasizes:
+  - name: key-principles
+    description: "1. **Specification Before Code**: Define requirements and constraints clearly 2. **Design Before Implementation**: Plan architecture and components 3. **Tests Before Features**: Write failing tests, then make them pass 4. **Review Everything**: Code quality, security, and performance checks 5. **Doc"
+    tools: ["bash", "read"]
+    prompt: |
+      1. **Specification Before Code**: Define requirements and constraints clearly 2. **Design Before Implementation**: Plan architecture and components 3. **Tests Before Features**: Write failing tests, then make them pass 4. **Review Everything**: Code quality, security, and performance checks 5. **Doc
+  - name: development-phases
+    description: "Development Phases"
+    tools: ["bash", "read"]
+    prompt: |
+      Development Phases
+  - name: specification
+    description: "**Goal**: Define requirements, constraints, and success criteria"
+    tools: ["bash", "read", "grep", "mcp:agentic-qe:*"]
+    prompt: |
+      **Goal**: Define requirements, constraints, and success criteria
+  - name: architecture
+    description: "**Goal**: Design system structure and component interfaces"
+    tools: ["bash", "read"]
+    prompt: |
+      **Goal**: Design system structure and component interfaces
+  - name: refinement-tdd-implementation
+    description: "**Goal**: Implement features with test-first approach"
+    tools: ["bash", "read"]
+    prompt: |
+      **Goal**: Implement features with test-first approach

package/.opencode/skills/qe-stream-chain.yaml

@@ -0,0 +1,45 @@
+name: qe-stream-chain
+description: "Stream-JSON chaining for multi-agent pipelines, data transformation, and sequential workflows"
+minModelTier: tier2-good
+tags: ["streaming", "pipeline", "chaining", "multi-agent", "workflow", "qe", "quality-engineering"]
+steps:
+  - name: overview
+    description: "Stream-Chain provides two powerful modes for orchestrating multi-agent workflows:"
+    tools: ["bash", "read"]
+    prompt: |
+      Stream-Chain provides two powerful modes for orchestrating multi-agent workflows:
+  - name: run-a-custom-chain
+    description: "Run a Custom Chain"
+    tools: ["bash", "read"]
+    prompt: |
+      Run a Custom Chain
+  - name: execute-a-pipeline
+    description: "Execute a Pipeline"
+    tools: ["bash", "read"]
+    prompt: |
+      Execute a Pipeline
+  - name: custom-chains-run
+    description: "Execute custom stream chains with your own prompts for maximum flexibility."
+    tools: ["bash", "read"]
+    prompt: |
+      Execute custom stream chains with your own prompts for maximum flexibility.
+  - name: syntax
+    description: "Syntax"
+    tools: ["bash", "read"]
+    prompt: |
+      Syntax
+  - name: options
+    description: "Options"
+    tools: ["bash", "read"]
+    prompt: |
+      Options
+  - name: how-context-flows
+    description: "Each step receives the previous output as context:"
+    tools: ["bash", "read"]
+    prompt: |
+      Each step receives the previous output as context:
+  - name: examples
+    description: "Examples"
+    tools: ["bash", "read", "edit"]
+    prompt: |
+      Examples

package/.opencode/skills/qe-tdd-london-chicago.yaml

@@ -0,0 +1,45 @@
+name: qe-tdd-london-chicago
+description: "Apply London (mock-based) and Chicago (state-based) TDD schools. Use when practicing test-driven development or choosing testing style for your context."
+minModelTier: tier2-good
+tags: ["tdd", "testing", "london-school", "chicago-school", "red-green-refactor", "mocks", "qe", "quality-engineering", "development-practices"]
+steps:
+  - name: tdd-cycle
+    description: "TDD Cycle"
+    tools: ["bash", "read"]
+    prompt: |
+      TDD Cycle
+  - name: school-comparison
+    description: "School Comparison"
+    tools: ["bash", "read"]
+    prompt: |
+      School Comparison
+  - name: chicago-school-state-based
+    description: "**Philosophy:** Test observable behavior through public API. Keep tests close to consumer usage."
+    tools: ["bash", "read"]
+    prompt: |
+      **Philosophy:** Test observable behavior through public API. Keep tests close to consumer usage.
+  - name: london-school-mock-based
+    description: "**Philosophy:** Test each unit in isolation. Focus on how objects collaborate."
+    tools: ["bash", "read"]
+    prompt: |
+      **Philosophy:** Test each unit in isolation. Focus on how objects collaborate.
+  - name: mixed-approach-recommended
+    description: "Mixed Approach (Recommended)"
+    tools: ["bash", "read"]
+    prompt: |
+      Mixed Approach (Recommended)
+  - name: -over-mocking-london
+    description: "❌ Over-Mocking (London)"
+    tools: ["bash", "read"]
+    prompt: |
+      ❌ Over-Mocking (London)
+  - name: -mocking-internals
+    description: "❌ Mocking Internals"
+    tools: ["bash", "read"]
+    prompt: |
+      ❌ Mocking Internals
+  - name: -test-pain-design-pain
+    description: "- Need many mocks? → Too many dependencies - Hard to set up? → Constructor does too much - Can't test without database? → Coupling issue"
+    tools: ["bash", "read"]
+    prompt: |
+      - Need many mocks? → Too many dependencies - Hard to set up? → Constructor does too much - Can't test without database? → Coupling issue

package/.opencode/skills/qe-technical-writing.yaml

@@ -0,0 +1,45 @@
+name: qe-technical-writing
+description: "Write clear, engaging technical content from real experience. Use when writing blog posts, documentation, tutorials, or technical articles."
+minModelTier: tier1-any
+tags: ["writing", "documentation", "communication", "blogs", "tutorials", "qe", "quality-engineering"]
+steps:
+  - name: opening-2-3-paragraphs
+    description: "- Hook: The problem or insight - Context: Why this matters - Promise: What they'll learn"
+    tools: ["bash", "read"]
+    prompt: |
+      - Hook: The problem or insight - Context: Why this matters - Promise: What they'll learn
+  - name: body-3-5-sections
+    description: "- One clear idea per section - Support with examples/code/data"
+    tools: ["bash", "read"]
+    prompt: |
+      - One clear idea per section - Support with examples/code/data
+  - name: closing
+    description: "- Key takeaway (1-2 sentences) - Action reader can take"
+    tools: ["bash", "read"]
+    prompt: |
+      - Key takeaway (1-2 sentences) - Action reader can take
+  - name: core-principles
+    description: "Core Principles"
+    tools: ["bash", "read"]
+    prompt: |
+      Core Principles
+  - name: words-to-cut
+    description: "Words to Cut"
+    tools: ["bash", "read"]
+    prompt: |
+      Words to Cut
+  - name: audience-specific-writing
+    description: "Audience-Specific Writing"
+    tools: ["bash", "read"]
+    prompt: |
+      Audience-Specific Writing
+  - name: for-developers
+    description: "- Lead with code or concrete problem - Show implementation details - Discuss trade-offs and alternatives - Link to repos or examples"
+    tools: ["bash", "read"]
+    prompt: |
+      - Lead with code or concrete problem - Show implementation details - Discuss trade-offs and alternatives - Link to repos or examples
+  - name: for-qaqe
+    description: "- Start with testing challenge - Show strategy, not just tools - Include risk assessment - Provide adaptable heuristics"
+    tools: ["bash", "read"]
+    prompt: |
+      - Start with testing challenge - Show strategy, not just tools - Include risk assessment - Provide adaptable heuristics

package/.opencode/skills/qe-test-automation-strategy.yaml

@@ -0,0 +1,35 @@
+name: qe-test-automation-strategy
+description: "Design and implement effective test automation with proper pyramid, patterns, and CI/CD integration. Use when building automation frameworks or improving test efficiency."
+minModelTier: tier3-best
+tags: ["automation", "test-pyramid", "page-object", "first-principles", "ci-cd", "flaky-tests", "qe", "quality-engineering", "testing-methodologies"]
+steps:
+  - name: test-pyramid
+    description: "Test Pyramid"
+    tools: ["bash", "read"]
+    prompt: |
+      Test Pyramid
+  - name: first-principles
+    description: "F.I.R.S.T. Principles"
+    tools: ["bash", "read", "edit"]
+    prompt: |
+      F.I.R.S.T. Principles
+  - name: page-object-model
+    description: "Page Object Model"
+    tools: ["bash", "read"]
+    prompt: |
+      Page Object Model
+  - name: cicd-integration
+    description: "CI/CD Integration"
+    tools: ["bash", "read"]
+    prompt: |
+      CI/CD Integration
+  - name: flaky-test-management
+    description: "Flaky Test Management"
+    tools: ["bash", "read", "edit"]
+    prompt: |
+      Flaky Test Management
+  - name: agent-assisted-automation
+    description: "Agent-Assisted Automation"
+    tools: ["bash", "read"]
+    prompt: |
+      Agent-Assisted Automation

package/.opencode/skills/qe-test-data-management.yaml

@@ -0,0 +1,45 @@
+name: qe-test-data-management
+description: "Strategic test data generation, management, and privacy compliance. Use when creating test data, handling PII, ensuring GDPR/CCPA compliance, or scaling data generation for realistic testing scenarios."
+minModelTier: tier3-best
+tags: ["test-data", "faker", "synthetic", "gdpr", "pii", "anonymization", "factories", "qe", "quality-engineering", "specialized-testing"]
+steps:
+  - name: data-strategies
+    description: "Data Strategies"
+    tools: ["bash", "read"]
+    prompt: |
+      Data Strategies
+  - name: privacy-techniques
+    description: "Privacy Techniques"
+    tools: ["bash", "read"]
+    prompt: |
+      Privacy Techniques
+  - name: synthetic-data-generation
+    description: "Synthetic Data Generation"
+    tools: ["bash", "read"]
+    prompt: |
+      Synthetic Data Generation
+  - name: test-data-builder-pattern
+    description: "Test Data Builder Pattern"
+    tools: ["bash", "read"]
+    prompt: |
+      Test Data Builder Pattern
+  - name: data-anonymization
+    description: "Data Anonymization"
+    tools: ["bash", "read", "edit"]
+    prompt: |
+      Data Anonymization
+  - name: database-transaction-isolation
+    description: "Database Transaction Isolation"
+    tools: ["bash", "read"]
+    prompt: |
+      Database Transaction Isolation
+  - name: volume-data-generation
+    description: "Volume Data Generation"
+    tools: ["bash", "read"]
+    prompt: |
+      Volume Data Generation
+  - name: agent-driven-data-generation
+    description: "Agent-Driven Data Generation"
+    tools: ["bash", "read"]
+    prompt: |
+      Agent-Driven Data Generation