hal

Routes incoming requests to appropriate AI team members via Agent protocol.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/jedrecord/hal2026 --skill hal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hal
Source: https://github.com/jedrecord/hal2026/tree/main/skills/hal
Command: npx skills add https://github.com/jedrecord/hal2026 --skill hal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hal acts as the single point of contact for all requests, ensuring work is delegated to the correct AI team member and that results are tracked and reported instead of being executed directly.

Core Features & Use Cases

  • Delegation to specialists based on roster and capabilities
  • Enforced guardrails to prevent Hal from performing the work directly
  • Context-aware orchestration using Learnings.md and project-status to avoid conflicts
  • Scalable handling of multi-step tasks across a team, with clear reporting and escalation paths

Quick Start

Tell Hal to route a task by issuing the /hal command followed by your description.

Frequently Asked Questions about hal

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

FAQPage Schema
How do I orchestrate and route requests to multiple AI agents?

AI agent orchestration routes incoming requests to the appropriate team member based on roster capabilities, dispatching work via the Agent protocol while tracking outcomes through the completion-status protocol.

What is the best way to enforce delegation guardrails for a multi-agent workflow?

Delegation guardrails prevent the orchestrator from executing tasks directly, ensuring work is strictly dispatched to specialized agents based on enforced routing rules and tracked project status.

How do I delegate multi-step tasks across an AI team roster?

Multi-step task delegation reads the agent roster and capabilities to dispatch work sequentially, using Learnings.md and project-status context to avoid conflicts and report final outcomes.

Can I track project status and avoid conflicts during AI agent orchestration?

Context-aware orchestration uses Learnings.md and project-status files to track ongoing work, preventing delegation conflicts and ensuring proper reporting via the completion-status protocol.

Why does my AI orchestrator execute tasks directly instead of delegating them?

Executing tasks directly violates enforced delegation guardrails; the orchestrator must read the roster, dispatch work via the Agent protocol, and report outcomes using the completion-status protocol.

Do I need a pre-defined agent roster to use AI workflow delegation?

Yes, agent workflow delegation requires a defined roster and agent capabilities file to correctly route requests, enforce guardrails, and track multi-step task outcomes.