Claude Code adapter — generated by scripts/sync-plugin-support.js, do not edit. Canonical source: prompts/al-agent.create.prompt.md (sha256 c5220663504e12fbfc07c2b24fa71f0b5922acdf7a7eef0ef0c794c1aa3f93c3). This workflow was written for @workspace use … in GitHub Copilot Chat. Apply these harness mappings and treat everything else as binding:

Copilot surface in the contract	Claude Code equivalent
#runSubagent / runSubagent / agents:	The Task tool with subagent_type: "aldc:<agent>"; one invocation carries everything inline (subagents are stateless)
#askQuestions / vscode/askQuestions	AskUserQuestion (main session only; a subagent returns its questions in its structured output)
handoffs: entries, and send: false on one	No equivalent — the gate is yours to keep. In Copilot a handoff is a button the human clicks, and send: false additionally hands them the prompt to review before it is sent; the host supplies the approval. Claude Code delegates through the Task tool, with no click and no review step. So never auto-delegate: present your output, get explicit approval, and only then delegate or route to another role. The handoff's routing is carried by the plugin's role entry skills; its human gate is carried by this rule
@al-architect, @al-spec-agent, @al-conductor, @al-developer, @al-developer-reviewer, @al-triage, @al-presales, @al-agent-builder, @dredd	/aldc:architect, /aldc:spec, /aldc:conduct, /aldc:develop, /aldc:review, /aldc:triage, /aldc:presales, /aldc:agent-builder, /aldc:audit (or claude --agent aldc:<agent>)
@workspace use <workflow>	/aldc:<workflow> with dots replaced by dashes (al-spec.create -> /aldc:al-spec-create); already rewritten below
${input:Name} prompt variables	Take the value from $ARGUMENTS; ask through AskUserQuestion when missing. Already rewritten below as <Name from $ARGUMENTS>
execute / runInTerminal, AL compilation or symbol restore	Developer/Implementer: discovered official AL MCP mcp__al__al_compile / mcp__al__al_build / mcp__al__al_downloadsymbols, or an installed ALTool/AL-Go runner through Bash. Use the correct App/Test project; unavailable capabilities are never simulated. Publishing retains its separate human/CI gate and is not granted by this adapter
edit, read/readFile, search, #codebase	Edit/Write, Read, Grep/Glob
#changes, changes, search/changes	Read-only git status / git diff through Bash only where granted; otherwise read the caller-supplied diff artifact or return the missing evidence request
read/problems, al_get_diagnostics, #testFailure	Discovered mcp__al__al_getdiagnostics for the explicit project, or actual compiler/test output. Diagnostics are not evidence of a fresh compile or executed tests. No result: record not-run / unavailable
al-symbols-mcp/*, upstash/context7/*, microsoft-learn/*, microsoft-docs/*	Tools named mcp__al-symbols-mcp__*, mcp__context7__*, mcp__microsoft-docs__* (or the mcp__plugin_aldc_… form). A server that is not loaded is unavailable; do not simulate it
sshadowsdk.al-lsp-for-agents/*, #usages, semantic definition/reference queries	Claude LSP with the existing AL LSP for Agents companion; discover the actual operations and project context first. VS Code tool identifiers are not Claude tool names
ms-dynamics-smb.al/*, vscode.mermaid-chat-features/*	VS Code tool identifiers do not exist here. Use only a separately discovered Claude capability; never rename community tools as Microsoft tools
vscode/memory, vscode/*	Not available; keep state in the canonical .claude/plans/ artifacts of the project
todo	TodoWrite for in-session tracking; durable state stays in .claude/plans/
"load skill-x"	The Skill tool (aldc:<skill-name>) or read ${CLAUDE_PROJECT_DIR}/.claude/skills/<skill-name>/SKILL.md
.github/instructions/*.instructions.md (applyTo)	${CLAUDE_PROJECT_DIR}/.claude/rules/*.md (paths:); /aldc:al-initialize copies them to the project's .claude/rules/ for auto-apply in the main session; inject inline for subagents exactly as the contract says
.github/skills/, .github/plans/…, docs/templates/	${CLAUDE_PROJECT_DIR}/.claude/skills/, .claude/plans/… (project-owned, aldc.yaml -> plans.root), ${CLAUDE_PROJECT_DIR}/claude-plugin/docs/templates/; already rewritten below
python … runtime helpers, --aldc-root	Paths already point at ${CLAUDE_PLUGIN_ROOT}; use python or python3, whichever exists (stdlib only)
aldc.yaml	${CLAUDE_PROJECT_DIR}/aldc.yaml when the project has one, otherwise ${CLAUDE_PROJECT_DIR}/claude-plugin/aldc.yaml

Read ${CLAUDE_PROJECT_DIR}/claude-plugin/docs/claude-al-tooling.md for this surface’s LSP/MCP bindings, then ${CLAUDE_PROJECT_DIR}/.claude/skills/skill-migrate/references/cli-al-tools.md for the shared role/evidence contract. The Claude guide supersedes older capability-availability examples, never role responsibilities or human gates.

Workflow: Create Coded Agent (Agent SDK)

End-to-end orchestration to produce a production-ready agent. This prompt does not contain SDK knowledge — it applies patterns from the loaded skills:

• skill-agent-toolkit → registration, 3 interfaces, Setup Codeunit, ConfigurationDialog, project structure
• skill-agent-task-patterns → Patterns A–H for task integration (Phase 6)
• skill-agent-instructions → Responsibilities-Guidelines-Instructions framework (Phase 7)

Human validation gates

🛑 markers require human approval before proceeding to the next phase.

Phase 1 — Agent specification

1.1 Gather requirements

Ask the developer:

1. Agent purpose — business process being automated
2. Creation rules — single instance? multi? always?
3. Trigger type — manual (page action) / EventSubscriber / email / mixed?
4. Data scope — tables and pages the agent needs access to
5. Setup properties — any agent-specific configuration beyond standard?
6. Message processing — input validation? output post-processing?
7. User intervention suggestions — what help options when stuck?
8. Summary KPIs — what metrics on hover card?
9. Annotations — what preconditions to validate (licensing, config completeness)?

1.2 Generate Agent Spec

# Agent Specification: {Agent Name}

## Identity
- Name: {Name}
- Initials: {3-4 chars}
- Object ID Range: {e.g. 52100-52199}

## Project Structure
See skill-agent-toolkit project structure section.

## Creation Rules
- Instance Model: {Single / Multi / Always}

## Interfaces
### IAgentFactory
- Setup Page: Page {ID} "{Agent} Setup" (ConfigurationDialog)
- Default Profile: {Profile ID}
- Default Permissions: {PermissionSet ID}

### IAgentMetadata
- Annotations: {precondition checks}
- Summary KPIs: {metrics for hover card}
- Custom Message Page: {Yes/No}

### IAgentTaskExecution
- Input Validation: {what to check}
- Output Post-Processing: {signatures, formatting}
- User Intervention Suggestions: {list}
- Page Context: {page-specific context}

## Task Integration
- Triggers: {events or page actions}
- ExternalId Pattern: {format}
- Patterns Applied: {A / B / C / D / E / F / G / H}

🛑 STOP — Review spec before proceeding.

Phase 2 — Registration + Integration

Apply: skill-agent-toolkit → "Registration — 4 required objects".

Generate:

1. Copilot Capability EnumExt — unique value ID
2. Metadata Provider EnumExt — links the 3 interface implementations
3. Install Codeunit — OnInstallAppPerDatabase, Unregister+Register, re-install instructions for existing setup records
4. Upgrade Codeunit — OnUpgradePerDatabase, instruction updates with UpgradeTag

🛑 STOP — Verify enum IDs are unique.

Phase 3 — Setup Infrastructure

Apply: skill-agent-toolkit → "Setup Codeunit" and "ConfigurationDialog page".

Generate:

1. Setup Table — PK = "User Security ID": Guid, DataPerCompany = false, custom fields
2. Setup Codeunit — GetInitials, GetSetupPageId, GetSummaryPageId, GetInstructions (SecretText), GetDefaultProfile, GetDefaultAccessControls, InitializeSetupRecord, SaveSetupRecord, SaveCustomProperties
3. ConfigurationDialog Page — invariants from the skill (SourceTableTemporary, AgentSetupPart first, AzureOpenAI check, system actions)

🛑 STOP — Review setup infrastructure.

Phase 4 — Interface implementations

Apply: skill-agent-toolkit → "The 3 core interfaces".

Generate the 3 codeunits delegating to Setup Codeunit. IAgentTaskExecution.AnalyzeAgentTaskMessage uses AgentMessage.GetText() / UpdateText() — never raw record fields.

🛑 STOP — Review interface implementations.

Phase 5 — Profile + Permissions + KPI

Generate:

1. Profile with RoleCenter reference
2. RoleCenter Page (PageType = RoleCenter) with navigation actions
3. PageCustomizations to tailor pages for the agent's view
4. PermissionSet including D365 BASIC + domain permissions
5. KPI Table (PK = User Security ID, custom KPI fields)
6. KPI Page (PageType = CardPart, cuegroup with metrics)

🛑 STOP — Review profile and permissions.

Phase 6 — Task Integration + Public API

Apply: skill-agent-task-patterns → relevant patterns (A always, plus B/C/D/E/H depending on spec). Verify each method against the API Availability Matrix before generating code.

Generate:

1. Public API codeunit (Access = Public) — Pattern A, with the standard overloads
2. Public API Impl codeunit (Access = Internal) — uses Agent Task Builder
3. Page Extension — example integration (Pattern B)
4. EventSubscriber codeunit — if Pattern C applies (TryFunction + telemetry)
5. Agent Session Events — if Pattern H applies (SingleInstance + BindSubscription)

🛑 STOP — Review task integration.

Phase 7 — Instructions + Tests

Apply: skill-agent-instructions → RGI framework + keywords. Apply: al-agent.test prompt for the test codeunit.

Generate:

1. InstructionsV1.txt — Responsibilities → Guidelines → Instructions, English, environment-agnostic
2. Test Codeunit — 6 categories (run al-agent.test)

🛑 STOP — Review instructions and tests.

Deliverables checklist

• {Agent}CopilotCapability.EnumExt.al
• {Agent}MetadataProvider.EnumExt.al
• {Agent}Install.Codeunit.al
• {Agent}Upgrade.Codeunit.al
• {Agent}Setup.Table.al
• {Agent}Setup.Codeunit.al
• {Agent}Setup.Page.al
• {Agent}Factory.Codeunit.al (implements IAgentFactory)
• {Agent}Metadata.Codeunit.al (implements IAgentMetadata)
• {Agent}TaskExecution.Codeunit.al (implements IAgentTaskExecution)
• {Agent}KPI.Table.al + {Agent}KPI.Page.al
• {Agent}Profile.Profile.al + {Agent}RoleCenter.Page.al
• {Agent}.permissionset.al
• {Agent}PublicAPI.Codeunit.al + Impl
• {Agent}*Ext.PageExt.al (example integration)
• .resources/Instructions/InstructionsV1.txt
• Test codeunit (6 categories)
• Agent specification document

Skills Evidencing

End the workflow declaring:

**Skills loaded**: skill-agent-toolkit, skill-agent-task-patterns, skill-agent-instructions
**Patterns applied**: {list each pattern with the file where it was applied}