hyper-san-output

Generate standardized HyperSan JSON output for sanity check workflows.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/AI-Driven-Highspeed-Development/adhd_framework_v3 --skill hyper-san-output
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hyper-san-output
Source: https://github.com/AI-Driven-Highspeed-Development/adhd_framework_v3/tree/main/modules/dev/instruction_core/data/skills/hyper-san-output
Command: npx skills add https://github.com/AI-Driven-Highspeed-Development/adhd_framework_v3 --skill hyper-san-output

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

HyperSan output contract provides a standardized, machine-parseable schema for sanity-check results, enabling reliable inter-agent communication and auditability.

Core Features & Use Cases

  • Defines severity and difficulty matrices, required issue fields, JSON schemas for subagent mode, and structured conversational output for direct mode.
  • Supports evaluation pass criteria and fix recommendations to guide remediation workflows across direct and subagent contexts.
  • Use Case: When producing HyperSan review results or parsing HyperSan output, or implementing sanity check workflows across multi-agent systems.

Quick Start

Run a HyperSan sanity validation workflow to produce a structured output document that conforms to the contract.

Frequently Asked Questions about hyper-san-output

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

FAQPage Schema
How do I standardize agent output for sanity checks?

Standardizing agent output for sanity checks involves applying a schema that enforces consistent JSON or conversational formats with required issue fields, severity matrices, and pass criteria for reliable machine parsing.

What is the HyperSan output contract used for?

The HyperSan output contract is used to provide a standardized, machine-parseable schema for sanity-check results, enabling reliable inter-agent communication and auditability across direct-user and subagent workflows.

How do I structure validation results for multi-agent systems?

Structure validation results for multi-agent systems by generating standardized HyperSan output that defines severity and difficulty matrices, required issue fields, and structured conversational formats for both direct and subagent contexts.

Does the HyperSan schema support severity levels and fix recommendations?

Yes, the HyperSan schema supports severity levels and fix recommendations by explicitly handling BLOCKER, WARNING, and SUGGESTION levels, and providing evaluation pass criteria to guide remediation workflows across verification tasks.

Can I use JSON Schema for subagent sanity check workflows?

Yes, you can use JSON Schema for subagent sanity check workflows to define required issue fields and severity matrices, producing a machine-parseable structured output document that satisfies subagent verification requirements.