qe-requirements-validation
Validates acceptance criteria for testability, traces requirements to test cases, and generates BDD scenarios from user stories. Use when validating acceptance criteria, building requirements traceability matrices, managing Gherkin scenarios, or ensuring complete requirements coverage before development.
What this skill does
# 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
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.