Microsoft Agent Framework

Microsoft Agent Framework

Ground Microsoft Agent Framework work in the latest official documentation, choose the correct .NET or Python reference, and apply up-to-date shared agent/workflow guidance without relying on stale Semantic Kernel or AutoGen assumptions.

When to invoke

• "Build a Microsoft Agent Framework agent."
• "Migrate this Semantic Kernel app to Agent Framework."
• "Migrate from AutoGen to Microsoft Agent Framework."
• "Review this Agent Framework workflow."
• "Show .NET or Python package guidance for Agent Framework."

Prerequisites and context

• Microsoft Agent Framework is in public preview and changes quickly.
• Read the official overview at https://learn.microsoft.com/agent-framework/overview/agent-framework-overview before making implementation choices.
• Prefer official docs and samples for current APIs; treat older Semantic Kernel and AutoGen code as migration input.
• Use live documentation tooling when available to fetch current framework guidance and examples.

Language routing

Shared implementation guidance

Migration guidance

Procedure

1. Determine the target language from files or the user's request.
2. Read references/dotnet.md or references/python.md for package names, repository paths, sample locations, and language-specific practices.
3. Fetch the latest official documentation and samples before recommending APIs.
4. Apply the shared guidance for agents, workflows, providers, state, and authentication.
5. If repository examples differ from current docs, explain the difference and follow the supported pattern unless the user asks for legacy compatibility.

Progressive disclosure and bundled resources

• references/dotnet.md: .NET-specific package, sample, and coding guidance.
• references/python.md: Python-specific package, sample, and coding guidance.

Gotchas

• Do not assume Semantic Kernel or AutoGen APIs are still correct: use official migration guides and current Agent Framework docs.
• Do not skip language routing: .NET and Python packages, samples, and idioms differ.
• Do not present preview APIs as stable contracts: call out documentation date sensitivity when relevant.

Open Horizons integration

• Scope Microsoft Agent Framework work to the seven application agents and current Horizon stage.
• Preserve the boundary between Microsoft Foundry application agents and GitHub Copilot harness agents.
• Route cross-domain sequencing through open-horizons-orchestration (skill).

Output template

## Microsoft Agent Framework result

**Status:** ready | needs docs lookup | blocked
**Language:** .NET | Python | mixed | unknown
**Task:** create | update | refactor | explain | review | migrate

| Decision | Recommendation | Source |
| --- | --- | --- |
| Language workflow | `<references/dotnet.md or references/python.md>` | <file signal or user request> |
| Agent/workflow pattern | <agent, workflow, provider, state, auth> | <official doc/sample> |
| Migration note | <Semantic Kernel, AutoGen, or none> | <guide or reason> |

### Validation
- <docs consulted, build/test result, or review evidence>

Quality gate

• The target language is determined before implementation advice is given.
• The matching bundled reference file was consulted for package names and sample paths.
• Current official Microsoft Agent Framework documentation was checked.
• Recommendations distinguish agents from workflows and name the provider/authentication pattern.
• Migration advice mentions Semantic Kernel or AutoGen only when relevant.
• Preview uncertainty or documentation mismatch is surfaced rather than hidden.

References

• Microsoft Agent Framework overview
• Migration guide from Semantic Kernel
• Migration guide from AutoGen