hara-stage3a

Generate Stage 3A operational scenarios and hazard events for a single MF.

2|Updated May 13, 2026
One-click install
npx skills add https://github.com/WSJ40/hara-mutiagent --skill hara-stage3a
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hara-stage3a
Source: https://github.com/WSJ40/hara-mutiagent/tree/main/skills/hara-stage3a
Command: npx skills add https://github.com/WSJ40/hara-mutiagent --skill hara-stage3a

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill generates Stage 3A operational scenarios and associated hazard events from a single MF-level Stage 3 context, producing validated JSON outputs for downstream processing.

Core Features & Use Cases

  • MF-scoped Scenario & Hazard Generation: Produces 10–20 realistic, non-duplicated scenarios and hazard events for one specified MF_ID only.
  • Contract-Strict JSON Output: Ensures the output matches the Stage 3A JSON contract (top-level keys, enumerations, structure, and reasoning subfields).
  • Max-Risk Planning First: Produces max_asil_planning before scenarios to cover credible highest-risk pathways and planning assumptions.
  • Field Inheritance Without Rewriting: Copies 故障描述 and 整车危害 verbatim from the MF in the Stage 3 context; does not generate S/E/C, ASIL, safety goals, or safety states.

Quick Start

Run this Skill to generate output/<RUN_ID>_stage3a_<MF_ID>_scenarios.json by reading output/<RUN_ID>_stage3_context_<MF_ID>.json and validating it with the provided Stage3A check command.

Frequently Asked Questions about hara-stage3a

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

FAQPage Schema
How do I generate Stage 3A operational scenarios and hazard events for automotive HARA?

To generate Stage 3A operational scenarios and hazard events for automotive HARA, process a single MF-level Stage 3 context to output 10–20 non-duplicated scenarios and hazard events in a validated JSON format.

What is the Stage 3A JSON contract for hazard analysis scenario generation?

The Stage 3A JSON contract for hazard analysis scenario generation requires filling only specific top-level keys, scenario enumerations, and reasoning subfields to satisfy deterministic validation requirements for downstream processing.

How do I ensure max ASIL planning covers credible highest-risk pathways before enumerating scenarios?

To ensure max ASIL planning covers credible highest-risk pathways, generate the max_asil_planning field before creating operational scenarios to establish planning assumptions for the specified MF_ID.

Does Stage 3A hazard generation require creating new safety goals or ASIL ratings?

Stage 3A hazard generation does not require creating new safety goals, ASIL ratings, S/E/C metrics, or safety states; it enforces verbatim inheritance of stage3_mf fault descriptions and vehicle-level hazards.

What input file format is needed to run MF-scoped hazard and scenario generation?

MF-scoped hazard and scenario generation requires reading an MF-level Stage 3 context JSON file, typically named output/<RUN_ID>_stage3_context_<MF_ID>.json, to produce the corresponding Stage 3A scenarios output.