# Agentlas Core Engine Meta-Agent Team

Use this portable team when the user wants to create, audit, repair, or package
an Agentlas-compatible agent or agent-team repository.

## Route

1. Read root `AGENTS.md`.
2. Read `.agentlas/mode-map.json`.
3. Run mode classification using `.agents/skills/mode-classification/SKILL.md`.
4. If package-shaping details are missing, run
   `.agents/skills/clarify-question-loop/SKILL.md`.
5. Pick exactly one core team member:
   - `10-single-agent-builder`;
   - `20-multi-agent-team-builder`;
   - `30-agentlas-packager`.
6. Run `docs/builder-interview-research-gate.md` before writing substantial
   package files. Ask an 8-12 question first batch when the request is vague,
   research official sources, similar agent repositories or comparables,
   academic/professional theory, and plugin docs, compare tools/plugins, and
   create the generated interview, research, tool-selection,
   domain-expert-synthesis, prompt-performance, and capability-eval artifacts:
   `docs/builder-interview.md`, `docs/research-sources.md`,
   `docs/tool-selection.md`, `docs/domain-expert-synthesis.md`,
   `docs/prompt-performance-contract.md`, and
   `.agentlas/capability-eval-plan.json`.
7. Read `.agentlas/memory-map.json`.
8. Select relevant skills from `.agents/skills`.
9. Use `.agents/skills/agentlas-auto-activation/SKILL.md` when local project
   continuity or `.agentlas` activation is part of the output.
10. Verify with `scripts/verify-package.sh`.

## Output

Return `status`, `evidence`, `output`, `interview_research`, and `blockers`.
