[New Mission] Operative NextGen: Build skills and connected agents

[aprildunnam]

[New Mission] Operative NextGen: Build skills and connected agents

Summary

Author the multi-agent mission where learners create, ground, connect, and evaluate the Interview Prep Agent. Teach skills for focused in-agent behavior and connected agents for independently owned, published specialists; remove classic child-agent guidance.

Mission 02 establishes the Hiring Agent baseline and Dataverse MCP. This mission adds the reusable Interview Prep Agent and proves orchestration between agents. Duplicate checks found no issue proposing this complete Operative NextGen mission.

Proposed mission

Field	Value
Section	Operative NextGen
Folder	docs/operative-v2/03-multi-agent/
Title	Mission 03: Multi-Agent Systems: Skills and Connected Agents
Operation codename	OPERATION SYMPHONY
Difficulty	2
Time	60 minutes

Scenario

The Hiring Agent cannot own every hiring responsibility. The learner builds an Interview Prep Agent with its own instructions, grounding, settings, and lifecycle, then connects it to the Hiring Agent while retaining skills for focused behavior within the orchestrator.

Use an organization analogy: skills are playbooks inside one team; connected agents are independent specialist teams collaborating through a defined handoff.

Mission objectives

• Choose between skills and connected agents.
• Build and ground the Interview Prep Agent.
• Publish and connect it to the Hiring Agent.
• Write clear delegation and handoff instructions.
• Evaluate routing, context, and response quality.

Prerequisites to state in the mission

• Completion of Missions 01 and 02.
• Seeded Job Roles and Evaluation Criteria.
• Dataverse MCP access.
• Permission to create, publish, and connect agents.

Proposed lab outline

Design the architecture

Compare skills and connected agents by ownership, tools, knowledge, deployment, reuse, authentication, and evaluation. Map the Hiring Agent and Interview Prep Agent responsibilities.

Build and ground Interview Prep

Create the Interview Prep Agent in the Operative solution. Write instructions for candidate and role analysis, add only required Dataverse MCP capabilities, and test direct behavior.

Connect and orchestrate

Publish Interview Prep, add it as a connected agent, write a precise description and Hiring Agent delegation instructions, and verify that unrelated requests remain with the orchestrator.

Evaluate the system

Create routing tests for interview prep, resume intake, general hiring questions, missing context, and out-of-scope requests. Compare direct-agent and orchestrated responses and correct routing overlap.

Acceptance criteria

• Remove all child-agent creation instructions and explain the modern architecture explicitly.
• Create Interview Prep as an independently published connected agent, not a skill.
• Keep focused Hiring Agent procedures as skills and explain why.
• Ground Interview Prep only in the required hiring data.
• Verify current context-sharing behavior rather than documenting a removed toggle.
• Write non-overlapping skill and connected-agent descriptions.
• Test successful delegation, non-delegation, missing-data handling, and return to the Hiring Agent.
• Add a repeatable multi-agent evaluation set and record results.
• Capture current Build, Preview, and Evaluate screenshots.
• Preserve <mission-meta /> and the Operative Mission 03 analytics tag.
• Follow repository writing and validation standards.

Out of scope

• Resume parsing and application creation.
• Interview document generation.
• Calendar scheduling.
• Complex multi-hop agent networks.

Risks

• Overlapping descriptions can route requests to the wrong capability.
• Unpublished connected-agent changes are invisible to the caller.
• Shared context can expose unnecessary candidate information.
• Dataverse permissions can differ between agents and users.

References

• Operative v2 multi-agent mission
• Connected agents
• Authoring instructions
• Evaluate agents