What is the Reqvire framework used by this skill?

Reqvire is a requirements-as-context framework that allows engineering teams to manage specifications as structured Markdown files within their codebase, enabling version-controlled MBSE.

How does the skill handle requirement traceability?

It uses specific relationship types like 'satisfiedBy', 'verifiedBy', and 'derivedFrom' to create a clear audit trail from high-level user needs down to specific lines of code.

Can this skill analyze the impact of code changes?

Yes, by using the 'change-impact' command with Git integration, it can identify which requirements are affected by specific commits or code modifications.

What are EARS patterns in this context?

EARS stands for Easy Approach to Requirements Syntax. The skill uses these standardized templates (Ubiquitous, Event-driven, etc.) to ensure requirements are clear, testable, and unambiguous.

System & Requirements Engineer

Name: System & Requirements Engineer
Author: reqvire-org

byreqvire-org

•

Productivity & Workflow

Automates Model-Based Systems Engineering (MBSE) and requirements management using the Reqvire framework.

About

The System & Requirements Engineer skill transforms Claude into an expert MBSE architect, enabling teams to maintain high-fidelity engineering models directly within their repositories. By orchestrating the Reqvire CLI, it facilitates the entire requirements lifecycle—from capturing stakeholder needs to ensuring full implementation traceability. It is particularly useful for complex projects where maintaining a clear link between business requirements, system specifications, and code implementation is critical for compliance and technical clarity.

Key Features

4 GitHub stars
Deep context gathering by traversing requirement ancestor chains and attachments
Change impact analysis using Git history to track requirement drifts
Full MBSE traceability orchestration (User Needs to System Requirements to Code)
Automated EARS (Easy Approach to Requirements Syntax) pattern generation
Model validation and linting to ensure structural integrity and coverage

Use Cases

Refactoring cluttered project models into structured specifications with proper traceability
Ensuring regulatory compliance by linking code commits to specific verification methods
Generating granular implementation tasks from high-level requirement changes

About

Key Features

4 GitHub stars
Deep context gathering by traversing requirement ancestor chains and attachments
Change impact analysis using Git history to track requirement drifts
Full MBSE traceability orchestration (User Needs to System Requirements to Code)
Automated EARS (Easy Approach to Requirements Syntax) pattern generation
Model validation and linting to ensure structural integrity and coverage

Use Cases

Refactoring cluttered project models into structured specifications with proper traceability
Ensuring regulatory compliance by linking code commits to specific verification methods
Generating granular implementation tasks from high-level requirement changes