loom-requirement-analysis

Analyzes SystemWeaver requirements and SWCs to produce signal maps and test case guidance.

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/deriye/.agents-work --skill loom-requirement-analysis-deriye
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: loom-requirement-analysis
Source: https://github.com/deriye/.agents-work/tree/main/skills/loom-requirement-analysis
Command: npx skills add https://github.com/deriye/.agents-work --skill loom-requirement-analysis-deriye

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Automotive engineers working with SE-TOOL/SystemWeaver struggle to understand what a requirement or Software Component (SWC) actually does, especially when internal signals hide the real physical signal chains across requirements and SWCs. This Skill performs deep requirement analysis so test engineers and developers get a complete, unambiguous picture before writing test cases or code. ## Core Features & Use Cases - Full Signal Chain Resolution: Resolves every internal signal to its producer and consumer requirements, tracing back to physical CAN/LIN inputs and outputs, including cross-SWC and loopback detection. - Ambiguity Detection: Systematically checks against a catalog of 22 known ambiguity types (missing operators, undefined thresholds, shared output arbitration gaps) with severity ratings. - Structured Reports and Diagram Specs: Generates a comprehensive analysis report plus machine-readable JSON diagram specifications for downstream Mermaid rendering. - Use Case: Given a swap:// URL or XID like x0400000000A03F2A, the Skill retrieves the requirement context from SystemWeaver via Loom MCP tools, classifies the requirement pattern, maps all signals, flags specification gaps, and outputs test case guidance. ## Quick Start Analyze the requirement at swap://setoolvbc.srv.volvo.com:3001/x0400000000A03F2A and give me a full signal map with test case recommendations.

Frequently Asked Questions about loom-requirement-analysis

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

FAQPage Schema
How do I analyze a SystemWeaver requirement from an XID or swap:// URL?▼

Provide the XID (e.g., x0400000000A03F2A) or a swap:// URL, and the Skill extracts the XID, retrieves baselines and full requirement context via Loom MCP tools, then produces a structured analysis report with signal maps and test guidance.

How to trace internal signals across SWCs in SystemWeaver?▼

The Skill scans sibling requirements within the same SWC to find producers and consumers of each internal signal, then searches across SystemWeaver for cross-SWC variants. Unresolved signals are explicitly marked so test engineers know they must stub or simulate them.

What happens if the XID is a container instead of a requirement?▼

Container or SWC-level XIDs return 'not found' from context tools. The Skill detects this, searches for child requirements by name, and asks you to provide a specific child requirement XID, noting the limitation in the report.

Does the analysis handle CAN loopback signals?▼

Yes. The Skill detects when a signal marked as input is actually transmitted by the host ECU itself, classifying it as a loopback rather than a physical input. It documents the feedback path, CAN frame, and timing implications for testing.

What kinds of requirement ambiguities does it detect?▼

It checks against a catalog of 22 ambiguity types including missing comparison operators, undefined thresholds and timers, duplicate XIDs, shared output signals without arbitration rules, and unreliable direction metadata, each rated CRITICAL, HIGH, MEDIUM, or LOW.

What are the limitations of automated SystemWeaver requirement analysis?▼

Fuzzy database matches below 65% are treated as unknown routing, cross-SWC signal producers sometimes cannot be identified, and configuration parameter values referenced by name may require manual lookup from calibration teams. Unknowns are reported explicitly rather than assumed.