rnd-aspice-requirements-reviewer

Name: rnd-aspice-requirements-reviewer
Availability: InStock
Author: chendongqi

Review SYS.1, SYS.2, and SWE.1 documents for ASPICE compliance.

110|19|Updated Feb 11, 2026

Search Tags:#traceability #automotive #requirements-review #aspice #sys.1 #sys.2 #swe.1

Ready to run

npx skills add https://github.com/chendongqi/OPB-Skills --skill rnd-aspice-requirements-reviewer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rnd-aspice-requirements-reviewer
Source: https://github.com/chendongqi/OPB-Skills/tree/main/skills/rnd-aspice-requirements-reviewer
Command: npx skills add https://github.com/chendongqi/OPB-Skills --skill rnd-aspice-requirements-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a rigorous, structured ASPICE requirements review for SYS.1, SYS.2, and SWE.1 documents, ensuring compliance, completeness, and high-quality traceability.

Core Features & Use Cases

Thorough completeness, correctness, clarity, consistency, traceability, and testability checks across SYS.1/SYS.2/SWE.1 domains.
Structured review workflow with up-front information gathering, template conformance, and issue classification (Blocker/Major/Minor) producing a formal report.
Use Case: Audit a set of customer, system, and software requirements to identify gaps and generate remediation guidance.

Quick Start

In Claude Code, run the reviewer against your requirement document to generate a compliant ASPICE review report.

Frequently Asked Questions about rnd-aspice-requirements-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I review automotive requirements for ASPICE compliance?▼

ASPICE requirements review evaluates SYS.1, SYS.2, and SWE.1 documents for completeness, correctness, clarity, consistency, traceability, and verifiability. It enforces standardized templates and generates traceable, auditable reports capturing issues, impacts, and remediation guidance for automotive domains like intelligent cockpit and ADAS.

What is the best way to ensure traceability across SYS.1, SYS.2, and SWE.1 requirements?▼

The best way to ensure traceability across SYS.1, SYS.2, and SWE.1 requirements is conducting a structured review that maps customer, system, and software requirements. This identifies traceability gaps and generates formal reports with standardized templates for auditable remediation tracking.

How do I generate an ASPICE audit report for system and software requirements?▼

Generate an ASPICE audit report by running a structured review workflow that gathers information, checks template conformance, and classifies issues as Blocker, Major, or Minor. This produces a formal, auditable report capturing issues, impacts, and remediation recommendations for your requirement documents.

Does ASPICE requirements review work for ADAS and intelligent cockpit domains?▼

Yes, ASPICE requirements review is explicitly applied to automotive domains including intelligent cockpit, ADAS, and vehicle networks. It guides teams through completeness, correctness, clarity, consistency, traceability, and verifiability checks tailored to these specific domains.

What are the limitations of automated ASPICE requirements review?▼

Automated ASPICE requirements review is limited to SYS.1, SYS.2, and SWE.1 document evaluation and cannot replace human judgment for complex architectural decisions. It enforces template conformance and issue classification but requires teams to manually implement the remediation recommendations provided in the report.