hara-stage1r

Validate Stage 1 single-function failure semantics for a given Function_ID.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Stage1R ensures Stage 1 single-function failure semantics are correct and safe-boundary consistent by re-reviewing applicability, nan logic, missing safety-related failure types, and description edge cases per Function_ID.

Core Features & Use Cases

  • Function_ID-level semantic re-review: Confirms whether each failure entry is truly applicable to the current function’s functional essence and timing/size/direction boundaries.
  • nan correctness and safety boundary enforcement: Re-checks whether “nan” is justified with real evidence (not uncertainty) and whether “applicable but no safety risk” remains in Stage1 for Stage 2 filtering.
  • Review traceability without becoming structured input: Produces a per-function review artifact for human audit, and merges them into a total review via the merge tool.

Quick Start

Use the hara-stage1r skill to re-check output stage1 single-function JSON semantics for a specific Function_ID using the Stage1 context and mapping files, then write a Function_ID review JSON for human inspection.

Frequently Asked Questions about hara-stage1r

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

FAQPage Schema
How do I validate failure semantics for a specific function ID in a HARA pipeline?

To validate failure semantics for a function ID, re-check stage1 single-function JSON outputs by verifying applicability, nan logic, and boundary correctness against stage0 mapping and stage1 context.

What does nan validation mean in single-function failure semantics review?

Nan validation in failure semantics review means re-checking whether a nan designation is justified with real evidence rather than uncertainty, ensuring safety boundaries are correctly applied per function ID.

How do I re-review applicability and safety boundaries for stage1 failure types?

You re-review applicability by confirming each failure entry matches the current function's timing, size, and direction boundaries, then verify applicable but no safety risk entries remain for stage2 filtering.

Does the stage1 semantic review output act as a structured input for stage2 analysis?

No, stage1 semantic review does not act as a stage2 structured input. It produces per-function review artifacts for human audit that are later merged into a total review.

When do I need to run a failure semantics review at the Function_ID level?

You run a failure semantics review after stage1_slice passes, when you need to independently validate deterministic preconditions and ensure missing safety-related failure types are caught before merging.

Can I merge per-function review artifacts into a total review report?

Yes, per-function review artifacts can be merged into a total review using the merge tool, providing comprehensive traceability for human inspection without feeding into stage2 structured inputs.