consult

Files (1)

• SKILL.md

SKILL.md (first lines)

Load and follow the [Mops skill](../mops/SKILL.md), executing its `/multica-team:consult` flow
(FLOWS.md → Consult). An advisory session: answer the owner's question as an advisor with a
**zero standing footprint** — create nothing that outlives the session, keep answers sourced
and evidence-tiered, spin research (and, on request, validation) sub-agents ephemerally, and
offer to persist or projectize only when the answer leads there.

**Optional addressee** — `/multica-team:consult [who] <question>`: the contract is a property of the
conversation, so the default is **Team Advisor** but any addressee answers under it. Name a **team agent**
(answers from its own craft), an **expert** (its own voice and sources), or the **theatre**
(personas react — direction-only, 🎭-marked, registered nowhere — but a consulted validated twin
still logs its own use per its consent contract, MODULES → Persona theatre). Route to the **one**
addressee, no fan-out. Use the invocation arguments and accompanying user message as the request.

From junjiezhou1122/multica-team, MIT.

More from junjiezhou1122/multica-team