ahu-conductor

Coordinate multi-phase AHU design pipelines across HVAC tasks with QA gating.

Updated Dec 26, 2025
One-click install
npx skills add https://github.com/toneron2/RWS --skill ahu-conductor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ahu-conductor
Source: https://github.com/toneron2/RWS/tree/main/.claude/skills/ahu-conductor
Command: npx skills add https://github.com/toneron2/RWS --skill ahu-conductor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill acts as the orchestration brain for the RWS air handler design pipeline, coordinating specialized agents to deliver complete AHU designs efficiently and with traceable quality checks.

Core Features & Use Cases

  • Pipeline orchestration: Coordinate multi-agent tasks across design phases to deliver a full AHU design.
  • State management: Track design state through manifest files to ensure traceability.
  • Conflict resolution & QA gating: Resolve outputs when agents disagree and validate with QA before finalizing.
  • Use Case: Start a hospital AHU project and watch the conductor guide the pipeline from requirements through cost estimation.

Quick Start

Provide a detailed design request (location, capacity, OA fraction, and constraints) to initiate the AHU design pipeline.

Frequently Asked Questions about ahu-conductor

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

FAQPage Schema
How do I orchestrate a multi-agent HVAC design pipeline?

Multi-agent orchestration coordinates specialized agents across design phases to deliver complete AHU designs. This Skill acts as the conductor, managing requirements parsing, constraint derivation, component selection, integration, and QA validation across hospital, commercial, and data-center projects while tracking state through manifest files.

How do I manage state and traceability in AHU design workflows?

State management tracks design progression through manifest files, ensuring traceability across all pipeline phases. The conductor maintains design state, logs inter-agent communication, resolves conflicts when agents disagree, and gates outputs through QA before finalizing designs.

Can I use multi-agent orchestration for hospital and commercial HVAC projects?

Yes. This Skill applies to multi-phase HVAC design across hospital, commercial, and data-center settings, handling functional requirements like schema validation, conflict resolution, and QA gating specific to each context while coordinating parallel component selection and integration tasks.

How do I start an AHU design pipeline from requirements to cost estimation?

Provide a detailed design request including location, capacity, OA fraction, and constraints to initiate the pipeline. The conductor guides execution through all phases—from requirements parsing through constraint derivation, component selection, integration, and final QA—delivering a complete, validated design.

What happens when agents disagree during AHU design coordination?

Conflict resolution within the orchestration layer validates and reconciles agent outputs before QA gating. The conductor applies schema validation and traceability checks to ensure disagreements are resolved systematically, maintaining design integrity across multi-agent workflows.

Do I need to manage inter-agent communication manually in HVAC pipeline design?

No. The conductor handles inter-agent communication, state file generation, and coordination automatically across all design phases, eliminating manual handoff overhead while maintaining full traceability and QA validation throughout the pipeline.