houmao-specialist-mgr

Routes legacy Houmao specialist-manager requests to houmao-agent-definition while keeping help read-only.

18|3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/igamenovoer/houmao --skill houmao-specialist-mgr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: houmao-specialist-mgr
Source: https://github.com/igamenovoer/houmao/tree/main/src/houmao/agents/assets/system_skills/houmao-specialist-mgr
Command: npx skills add https://github.com/igamenovoer/houmao --skill houmao-specialist-mgr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It preserves older Houmao prompts and installed homes that still reference the houmao-specialist-mgr entry point, ensuring they continue to work by redirecting users to the canonical specialist skill.

Core Features & Use Cases

  • Compatibility handoff: Routes specialist, profile, create-agent-fast-forward, launch-agent, and stop-agent requests to houmao-agent-definition.
  • Read-only help: Provides help text without running commands, mutating files, sending mail, or changing agent lifecycle state.
  • Correct ownership boundaries: Avoids duplicating or claiming independent command behavior; uses houmao-agent-instance for broad live-agent lifecycle after launch/stop.

Quick Start

Ask your AI to explain what houmao-specialist-mgr can do, for example: "help me use houmao-specialist-mgr to create a specialist".

Frequently Asked Questions about houmao-specialist-mgr

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

FAQPage Schema
How do I maintain compatibility for legacy CLI workflows that call older agent orchestration commands?

To maintain compatibility for legacy CLI workflows, route older command requests to the canonical agent definition skill. This preserves backward compatibility for installed homes referencing legacy entry points without duplicating command ownership.

What is the correct way to handle workflow migration for specialist creation and launch-agent commands?

Workflow migration for specialist creation and launch-agent commands is handled by redirecting requests to the canonical specialist skill. This ensures correct ownership boundaries while keeping the wrapper strictly read-only and avoiding lifecycle changes.

Does the specialist management wrapper execute lifecycle changes or mutate files when handling stop-agent requests?

No, the specialist management wrapper does not execute lifecycle changes or mutate files when handling stop-agent requests. It provides read-only help and routes commands to the canonical skill to prevent unauthorized state modifications.

How do I redirect profile handling and create-agent-fast-forward requests without breaking existing prompt handoffs?

Redirect profile handling and create-agent-fast-forward requests by applying routing logic to the canonical agent definition skill. This ensures existing prompt handoffs resolve correctly while avoiding independent command behavior duplication.

Why does legacy specialist management terminology need a compatibility handoff for agent orchestration?

Legacy specialist management terminology needs a compatibility handoff because older prompts still reference deprecated entry points. The wrapper ensures these requests resolve to the canonical skill, preventing broken workflows during agent orchestration.

Can I use this compatibility wrapper to manage broad live-agent lifecycle state after launching agents?

No, you cannot use this wrapper to manage broad live-agent lifecycle state. After launching agents, use the dedicated agent instance skill for lifecycle management while this wrapper strictly handles compatibility routing.