hara-stage4r

Validate the operation mode field in Stage 4 SG_Sum JSON against HARA scenarios.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you verify that the model-filled “operation mode” in Stage 4 output is specific, non-placeholder, and consistent with the originating HARA scenario, without re-evaluating safety target semantics.

Core Features & Use Cases

  • Stage4 “操作模式” targeted review: Checks that “操作模式” is present, not a placeholder, and is a mode name rather than a long scene description.
  • Evidence-aligned consistency checks: Ensures the chosen mode aligns with the originating scenario described in Comments, referencing Stage3 HARA only for the relevant MF_ID when needed.
  • Guardrail-driven validation & repair: Runs Stage4 machine validation first, then allows controlled fixes that update only the “操作模式” field before exporting merge-ready results.

Quick Start

Ask the system to run Stage 4 machine validation and review the operation mode for output/<RUN_ID>_stage4_sg_sum.json, updating only the “操作模式” field if required.

Frequently Asked Questions about hara-stage4r

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

FAQPage Schema
How do I validate the operation mode in a Stage 4 HARA JSON output?

To validate the operation mode in a Stage 4 HARA JSON, run Stage 4 machine checks on the output file to ensure the mode is present, specific, and not a placeholder. This verifies consistency with the originating HARA scenario.

What is a Stage 4R operation mode consistency review?

A Stage 4R operation mode consistency review checks that the model-filled operation mode in a Stage 4 SG_Sum JSON is a specific mode name rather than a long scene description. It ensures alignment with the originating HARA scenario without re-evaluating safety target semantics.

Can I update safety targets and ASIL fields when fixing the operation mode in Stage 4 JSON?

No, when fixing the operation mode in Stage 4 JSON, you must only update the operation mode field. Safety targets, ASIL, safety state, and FTTI must remain consistent and untouched during the controlled repair process.

How do I repair a placeholder operation mode in a stage4_sg_sum.json file?

To repair a placeholder operation mode in a stage4_sg_sum.json file, run Stage 4 machine validation first, then perform a controlled fix that updates only the operation mode field. Consult Stage3 HARA references for the relevant MF_ID to ensure evidence-aligned consistency.

What are the limitations of automated Stage 4 operation mode repair?

Automated Stage 4 operation mode repair is limited to updating only the operation mode field and cannot modify safety targets, ASIL, safety state, or FTTI. It requires prior machine validation and does not re-evaluate safety target semantics.