moai-alfred-agent-guide

Select sub-agents and Haiku or Sonnet models for Alfred workflows.

1|Updated Jul 28, 2025
One-click install
npx skills add https://github.com/kivo360/quickhooks --skill moai-alfred-agent-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-alfred-agent-guide
Source: https://github.com/kivo360/quickhooks/tree/main/.claude/skills/moai-alfred-agent-guide
Command: npx skills add https://github.com/kivo360/quickhooks --skill moai-alfred-agent-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documents agent responsibilities, decision trees for agent selection, and Haiku vs Sonnet model guidance for orchestration.

Core Features & Use Cases

  • Agent Roster: 19 sub-agents with Haiku/Sonnet models
  • Decision Tree: Choose the right agent per task
  • Model Guidance: Haiku vs Sonnet model selection
  • Collaboration Patterns: Inter-agent coordination

Quick Start

Use the decision tree to pick spec-builder for SPEC planning.

Frequently Asked Questions about moai-alfred-agent-guide

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

FAQPage Schema
How do I route tasks to the right agent in a multi-agent orchestration system?

Multi-agent orchestration uses decision trees to route each task to the appropriate sub-agent based on task type and complexity. This Skill provides decision-tree logic for selecting among 19 sub-agents, ensuring each task reaches the agent best suited to handle it—whether for feature development, bug triage, code exploration, or documentation work.

When should I use Haiku versus Sonnet models in agent workflows?

Model selection depends on task complexity and latency requirements. Haiku handles simpler, faster tasks efficiently, while Sonnet tackles reasoning-heavy work. This Skill specifies model-choice criteria within Alfred workflows so agents automatically select the right model for each sub-task, balancing speed and capability.

What are the responsibility boundaries for agents in a multi-agent team?

Clear responsibility boundaries prevent duplicate work and ensure efficient collaboration. This Skill documents functional requirements and collaboration patterns for 19 sub-agents, defining what each agent owns and how agents coordinate when tasks span multiple domains.

How do decision trees improve agent selection in complex workflows?

Decision trees systematically narrow down agent choices by evaluating task attributes—scope, urgency, domain—against explicit rules. This Skill applies decision-tree routing across feature development, bug triage, code exploration, and documentation synchronization, eliminating guesswork and ensuring consistent dispatch logic.

Can I implement agent orchestration without predefined decision rules?

While possible, predefined decision rules ensure reliability and consistency at scale. This Skill provides explicit decision-tree specifications and responsibility boundaries for orchestrating 19 sub-agents, reducing errors and operational overhead compared to ad-hoc routing.