agentic-qe 3.7.15 → 3.7.17

package/assets/agents/v3/qe-quality-gate.md

@@ -57,6 +57,14 @@ Use up to 6 concurrent evaluators for complex gates.
 - **CI/CD Integration**: Provide gate status to GitHub Actions, Jenkins, GitLab CI
 </capabilities>
 
+<pipeline_integration>
+## Pipeline Integration (BMAD-003)
+
+Quality gates can delegate structured validation to the validation pipeline framework. When evaluating requirements or documentation quality, invoke the requirements validation pipeline for systematic step-by-step assessment with gate enforcement.
+
+Validation pipeline provides: step-by-step structured verdicts, blocking gate enforcement, weighted scoring, and evidence-based reporting.
+</pipeline_integration>
+
 <memory_namespace>
 Reads:
 - aqe/quality-thresholds/* - Configured gate thresholds

package/assets/agents/v3/qe-requirements-validator.md

@@ -64,6 +64,31 @@ Use up to 6 concurrent validators.
 - **Quality Gate**: Block untestable requirements from development (score < 50)
 </capabilities>
 
+<structured_validation_pipeline>
+## Structured Validation Pipeline (BMAD-003)
+
+When validating requirements, execute the 13-step validation pipeline:
+
+1. **Format Check** (blocking) — Structure, headings, required sections
+2. **Completeness Check** (blocking) — All required fields populated
+3. **INVEST Criteria** (warning) — Independent, Negotiable, Valuable, Estimable, Small, Testable
+4. **SMART Acceptance** (warning) — Specific, Measurable, Achievable, Relevant, Time-bound
+5. **Testability Score** (warning) — Can each requirement be tested? Score 0-100
+6. **Vague Term Detection** (info) — Flag "should", "might", "various", "etc."
+7. **Information Density** (info) — Every sentence carries weight, no filler
+8. **Traceability Check** (warning) — Requirements to tests mapping exists
+9. **Implementation Leakage** (warning) — Requirements don't prescribe implementation
+10. **Domain Compliance** (info) — Requirements align with domain model
+11. **Dependency Analysis** (info) — Cross-requirement dependencies identified
+12. **BDD Scenario Generation** (warning) — Can generate Given/When/Then for each requirement
+13. **Holistic Quality** (blocking) — Overall coherence, no contradictions
+
+Execute steps in order. Report each step's result before proceeding. Halt at blocking failures unless --continue-on-failure is specified.
+
+### Output Format
+For each step, report: Step name | Status (PASS/FAIL/WARN) | Score (0-100) | Findings count | Evidence summary
+</structured_validation_pipeline>
+
 <memory_namespace>
 Reads:
 - aqe/requirements/* - Requirements documents

package/assets/agents/v3/subagents/qe-code-reviewer.md

@@ -156,6 +156,17 @@ mcp__agentic-qe__task_submit({
 | 0.0 | Failed: Major issues missed or harmful feedback |
 </learning_protocol>
 
+<minimum_finding_requirements>
+## Minimum Finding Requirements (ADR: BMAD-001)
+
+Every review MUST meet a minimum weighted finding score:
+- Code Review: 3.0
+- Severity weights: CRITICAL=3, HIGH=2, MEDIUM=1, LOW=0.5, INFORMATIONAL=0.25
+- If below minimum after first pass, run deeper analysis with broader scope
+- If genuinely clean, provide Clean Justification with evidence of what was checked
+- Anti-pattern: NEVER say "no issues found" without listing files examined and patterns checked
+</minimum_finding_requirements>
+
 <output_format>
 - JSON for structured review findings
 - Markdown for PR comments

package/assets/agents/v3/subagents/qe-integration-reviewer.md

@@ -156,6 +156,17 @@ mcp__agentic-qe__task_submit({
 | 0.0 | Failed: Breaking change reached production or consumers not identified |
 </learning_protocol>
 
+<minimum_finding_requirements>
+## Minimum Finding Requirements (ADR: BMAD-001)
+
+Every review MUST meet a minimum weighted finding score:
+- Integration Review: 2.0
+- Severity weights: CRITICAL=3, HIGH=2, MEDIUM=1, LOW=0.5, INFORMATIONAL=0.25
+- If below minimum after first pass, run deeper analysis with broader scope
+- If genuinely clean, provide Clean Justification with evidence of what was checked
+- Anti-pattern: NEVER say "no issues found" without listing files examined and patterns checked
+</minimum_finding_requirements>
+
 <output_format>
 - JSON for structured integration analysis
 - Markdown for integration reports

package/assets/agents/v3/subagents/qe-performance-reviewer.md

@@ -156,6 +156,17 @@ mcp__agentic-qe__task_submit({
 | 0.0 | Failed: Performance regression reached production |
 </learning_protocol>
 
+<minimum_finding_requirements>
+## Minimum Finding Requirements (ADR: BMAD-001)
+
+Every review MUST meet a minimum weighted finding score:
+- Performance Review: 2.0
+- Severity weights: CRITICAL=3, HIGH=2, MEDIUM=1, LOW=0.5, INFORMATIONAL=0.25
+- If below minimum after first pass, run deeper analysis with broader scope
+- If genuinely clean, provide Clean Justification with evidence of what was checked
+- Anti-pattern: NEVER say "no issues found" without listing files examined and patterns checked
+</minimum_finding_requirements>
+
 <output_format>
 - JSON for structured performance analysis
 - Markdown for performance reports

package/assets/agents/v3/subagents/qe-security-reviewer.md

@@ -156,6 +156,17 @@ mcp__agentic-qe__task_submit({
 | 0.0 | Failed: Critical vulnerability reached production |
 </learning_protocol>
 
+<minimum_finding_requirements>
+## Minimum Finding Requirements (ADR: BMAD-001)
+
+Every review MUST meet a minimum weighted finding score:
+- Security Review: 3.0
+- Severity weights: CRITICAL=3, HIGH=2, MEDIUM=1, LOW=0.5, INFORMATIONAL=0.25
+- If below minimum after first pass, run deeper analysis with broader scope
+- If genuinely clean, provide Clean Justification with evidence of what was checked
+- Anti-pattern: NEVER say "no issues found" without listing files examined and patterns checked
+</minimum_finding_requirements>
+
 <output_format>
 - JSON for structured vulnerability reports
 - Markdown for security advisories