home / skills / proffesor-for-testing / agentic-qe / qe-requirements-validation

qe-requirements-validation skill

/v3/assets/skills/qe-requirements-validation

This skill validates requirements, traces coverage to tests, and generates BDD scenarios to ensure complete acceptance criteria across the SDLC.

npx playbooks add skill proffesor-for-testing/agentic-qe --skill qe-requirements-validation

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
5.3 KB
---
name: "QE Requirements Validation"
description: "Requirements traceability, acceptance criteria validation, and BDD scenario management for complete requirements coverage."
---

# QE Requirements Validation

## Purpose

Guide the use of v3's requirements validation capabilities including acceptance criteria parsing, requirements traceability, BDD scenario generation, and coverage gap identification.

## Activation

- When validating requirements
- When tracing requirements to tests
- When generating BDD scenarios
- When assessing requirements coverage
- When reviewing acceptance criteria

## Quick Start

```bash
# Parse acceptance criteria
aqe requirements parse --source jira --project MYAPP

# Build traceability matrix
aqe requirements trace --requirements reqs/ --tests tests/

# Generate BDD scenarios
aqe requirements bdd --story US-123 --output features/

# Check requirements coverage
aqe requirements coverage --sprint current
```

## Agent Workflow

```typescript
// Requirements validation
Task("Validate acceptance criteria", `
  Review acceptance criteria for sprint stories:
  - Check SMART criteria (Specific, Measurable, Achievable, Relevant, Testable)
  - Identify ambiguous requirements
  - Flag missing edge cases
  - Suggest improvements
`, "qe-acceptance-criteria")

// Traceability matrix
Task("Build traceability", `
  Create requirements traceability matrix:
  - Map user stories to test cases
  - Identify untested requirements
  - Find orphan tests (no linked requirement)
  - Calculate coverage metrics
`, "qe-traceability-builder")
```

## Requirements Operations

### 1. Acceptance Criteria Validation

```typescript
await acceptanceCriteria.validate({
  source: {
    type: 'jira',
    project: 'MYAPP',
    stories: 'sprint=current'
  },
  validation: {
    specific: true,
    measurable: true,
    achievable: true,
    relevant: true,
    testable: true
  },
  output: {
    score: true,
    issues: true,
    suggestions: true
  }
});
```

### 2. Traceability Matrix

```typescript
await traceabilityBuilder.build({
  requirements: {
    source: 'jira',
    types: ['story', 'task', 'bug']
  },
  artifacts: {
    tests: 'tests/**/*.test.ts',
    code: 'src/**/*.ts',
    documentation: 'docs/**/*.md'
  },
  output: {
    matrix: true,
    coverage: true,
    gaps: true,
    orphans: true
  }
});
```

### 3. BDD Scenario Generation

```typescript
await bddGenerator.generate({
  requirements: userStory,
  format: 'gherkin',
  scenarios: {
    happyPath: true,
    edgeCases: true,
    errorCases: true,
    dataVariations: true
  },
  output: {
    featureFile: true,
    stepDefinitions: 'skeleton'
  }
});
```

### 4. Coverage Analysis

```typescript
await requirementsCoverage.analyze({
  scope: 'sprint-23',
  metrics: {
    requirementsCovered: true,
    testCasesCoverage: true,
    automationCoverage: true,
    riskAssessment: true
  },
  report: {
    summary: true,
    details: true,
    recommendations: true
  }
});
```

## Traceability Matrix

```typescript
interface TraceabilityMatrix {
  requirements: {
    id: string;
    title: string;
    type: string;
    priority: string;
    status: string;
    linkedTests: string[];
    linkedCode: string[];
    coverage: 'full' | 'partial' | 'none';
  }[];
  tests: {
    id: string;
    name: string;
    type: 'unit' | 'integration' | 'e2e';
    linkedRequirements: string[];
    automated: boolean;
  }[];
  coverage: {
    requirementsCovered: number;
    requirementsPartial: number;
    requirementsUncovered: number;
    orphanTests: number;
  };
  gaps: {
    requirement: string;
    missingCoverage: string[];
    risk: 'high' | 'medium' | 'low';
  }[];
}
```

## BDD Integration

```gherkin
# Generated feature file
Feature: User Registration
  As a new user
  I want to create an account
  So that I can access the platform

  @happy-path
  Scenario: Successful registration with valid details
    Given I am on the registration page
    When I enter valid email "[email protected]"
    And I enter valid password "SecurePass123!"
    And I click the register button
    Then I should see a success message
    And I should receive a confirmation email

  @edge-case
  Scenario: Registration with existing email
    Given a user exists with email "[email protected]"
    When I try to register with email "[email protected]"
    Then I should see an error "Email already registered"
```

## Requirements Quality

```yaml
quality_checks:
  acceptance_criteria:
    has_given_when_then: preferred
    is_testable: required
    is_measurable: required
    no_ambiguity: required

  user_story:
    follows_template: "As a <role>, I want <feature>, so that <benefit>"
    has_acceptance_criteria: required
    estimated: preferred

  completeness:
    edge_cases_identified: required
    error_scenarios_covered: required
    non_functional_considered: preferred
```

## Sprint Integration

```typescript
await requirementsValidator.sprintReview({
  sprint: 'current',
  checks: {
    storiesComplete: true,
    criteriaValidated: true,
    testsLinked: true,
    coverageAdequate: true
  },
  gates: {
    minCoverage: 80,
    maxUntested: 2,
    requireDemo: true
  }
});
```

## Coordination

**Primary Agents**: qe-acceptance-criteria, qe-traceability-builder, qe-bdd-specialist
**Coordinator**: qe-requirements-coordinator
**Related Skills**: qe-test-generation, qe-quality-assessment

Overview

This skill provides requirements traceability, acceptance criteria validation, and BDD scenario management to ensure complete requirements coverage. It identifies gaps, generates Gherkin scenarios, and produces traceability matrices and coverage reports to drive test planning and risk reduction.

How this skill works

The skill parses requirements from sources like Jira, validates acceptance criteria against SMART and Given-When-Then patterns, and builds a requirements-to-tests traceability matrix. It generates BDD feature files and step-definition skeletons for happy paths, edge cases, and error cases, and analyzes coverage and orphan tests to produce actionable recommendations.

When to use it

  • Validating acceptance criteria before sprint start
  • Building or updating a requirements-to-tests traceability matrix
  • Generating BDD scenarios from user stories
  • Assessing sprint or release requirements coverage
  • Identifying untested or orphaned tests that increase risk

Best practices

  • Run acceptance criteria validation early in refinement to fix ambiguities
  • Require testable Given-When-Then or explicit acceptance steps for each story
  • Link tests to requirement IDs to maintain the traceability matrix automatically
  • Generate BDD scenarios for both happy path and edge/error cases to reduce regression risk
  • Set minimum coverage gates (e.g., 80%) and limit untested requirements per sprint

Example use cases

  • Parse Jira stories in a sprint and score acceptance criteria for testability and clarity
  • Build a traceability matrix mapping stories to unit/integration/e2e tests and source code
  • Auto-generate Gherkin feature files and step-definition skeletons for a user story
  • Analyze sprint coverage and output summary + recommended remediation for untested requirements
  • Flag orphan tests and identify requirements with partial or no automation

FAQ

What input sources are supported?

Primary support is for issue trackers such as Jira and local requirement files; tests, code, and documentation paths are configurable for traceability.

How are BDD scenarios generated?

The skill extracts user story intent and acceptance criteria, then creates Gherkin scenarios covering happy path, edge cases, error cases, and data variations, with optional step-definition skeletons.