declarative-agent-developer

原文涵盖的主题

• M365 Agent Developer
• Telemetry Tagging
• ⛔ Workspace Check — MANDATORY FIRST STEP
• 🚫 HARD REJECTION RULES — No Exceptions
• 🔍 Detect → Inform → Ask (Error-Handling Protocol)
• Phase Routing
• ATK CLI Setup
• Critical Rules

Before running any atk CLI commands, set the session environment variable so all CLI invocations are tagged as skill-initiated: Run this once at the start of the session. All subsequent atk commands in the same terminal will inherit it. Before doing ANYTHING, check the workspace files to fingerprint the project: 1. Run npx -y --package @microsoft/m365agentstoolkit-cli atk --version to confirm ATK CLI is installed. If not found → Stop. Tell the user to install ATK. 2. Check for m365agents.yml or teamsApp.yml at the project root. 3. Check for appPackage/declarativeAgent.json. 4. Check for non-agent indicators (package.json with express/react/next, src/index.js, app.py, etc.) Then follow the decision gate: | Condition | Gate | Action | |-----------|------|--------| | Non-agent project files, no appPackage/ | Reject | Text-only response. No files, no commands. | | No manifest, user wants to edit/deploy | Reject | Text-only response. Explain manifest is missing. | | No manifest, user wants new project | Scaffold | → Scaffolding Workflow | | Manifest exists with errors | Fix | Detect → Inform → Ask (see below). Do NOT deploy. | | Valid project, user reports behavior issues | Review | → I

这里只展示节选，请以完整原文和当前要求为准。