sfh-conductor

Orchestrate the SFH-OS 5-phase horn design pipeline from acoustic parameters to verified production.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates the entire SFH-OS pipeline, managing global state, resolving conflicts between acoustic and manufacturing demands, and orchestrating iterations across AG-GEN, AG-SIM, AG-MFG, AG-QA, and AG-VIZ.

Core Features & Use Cases

  • End-to-End Orchestration: Manages the 5-phase pipeline from generation to verification.
  • Conflict Resolution: Balances acoustic ideals with manufacturability constraints.
  • Iteration Control: Decides when to continue optimizing vs. accept convergence.

Quick Start

Trigger the full pipeline to design a horn by invoking the 5-phase process, or run individual phases as needed.

Frequently Asked Questions about sfh-conductor

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

FAQPage Schema
How do I orchestrate an end-to-end horn design pipeline from acoustic parameters to production?

Orchestrate the full SFH-OS pipeline by invoking the 5-phase workflow, which coordinates generation, simulation, manufacturing, quality assurance, and visualization stages. The conductor manages state across all phases, resolves conflicts between acoustic ideals and manufacturability, and tracks costs to deliver production-ready horn designs.

How do I handle conflicts between acoustic optimization and manufacturing constraints in horn design?

The orchestration layer implements conflict mediation that balances acoustic performance requirements against manufacturing feasibility. It evaluates trade-offs, applies budget-aware decision logic, and iterates between acoustic validation and fabrication constraints until convergence on a manufacturable design.

When should I continue iterating versus accepting a converged horn design?

Iteration control logic evaluates convergence criteria across acoustic validation, cost tracking, and manufacturing constraints. The conductor decides whether further optimization improves innovation parity or if the current design meets all verified requirements and should proceed to production.

Can I run individual pipeline phases separately or must I execute the full 5-phase workflow?

You can trigger the complete end-to-end pipeline or invoke individual phases—generation, simulation, manufacturing, QA, and visualization—as needed. The state-management system maintains consistency across partial runs and orchestrates sub-agent coordination regardless of execution mode.

What does state-management in a fractal horn pipeline handle?

State-management tracks design parameters, acoustic validation results, manufacturing feedback, cost allocations, and design iterations across all pipeline phases. It ensures global consistency, enables conflict resolution, and supports budget-aware decision-making throughout the horn design workflow.