/al-context-create

description: Generate or update context.md file documenting project structure, architecture, and key patterns for AI assistants and developers. ALDC workflow (Copilot prompt al-context.create); invoke explicitly.
disable-model-invocation: true

> **Copilot CLI adapter — generated; do not edit this distribution.** > Select a role using /agent or copilot --agent <id>. Role names in this contract > are routing destinations, never chat mentions or evidence of an invocation. > Delegate only through the native task tool, using the exact discovered agent ID > as agent_type (for example al-planning-subagent). Inspect list_agents and the > actual task schema first. Keep all canonical human gates. Pass bounded context > inline; wait for completion (read_agent for a background task) before consuming > the result. A delegated role returns questions to its caller for the human gate. > If task or the requested custom agent is unavailable in this context, return > the blocked handoff to the caller/user. Never impersonate a missing subagent, > silently substitute general-purpose, or launch another CLI process to fake it. > Tool aliases in frontmatter select capabilities; call the actual tools exposed > by the host: view, glob, grep/rg, edit/create/apply_patch, bash/powershell, > web_fetch, task. Use a capability only when granted to this role and available. > Load domain skills through the host's skill mechanism when exposed, otherwise > read the complete bundled SKILL.md. A read is not a native skill invocation. > Resolve PLUGIN_ROOT to this installed agent's plugin directory (not the project > or original checkout). It is a path placeholder here, not a promised global > shell variable. Read docs/copilot-cli-al-tooling.md there for LSP/MCP bindings; > it supersedes older availability examples in the shared terminal contract at > skills/skill-migrate/references/cli-al-tools.md, never role duties or human gates. > Project instructions and matching .github/instructions rules remain binding; > pass the relevant excerpts to delegated roles. Canonical artifacts remain in > .github/plans/. Role write scopes are behavioral, not filesystem sandboxes. > AL execution requires a verified terminal command/runner or an actually exposed > MCP capability. Reuse the configured AL LSP for Agents wrapper through native > CLI semantic tools when exposed to this role. Inspect the catalog; do not invent > tool aliases or broaden read-only grants to enable rename/write operations. > Editor debugger controls remain separate from semantic navigation. Official AL > MCP selectors use al/<tool>; only Developer/Implementer receive compile/build/ > restore. Discover the actual callable names and pass the correct App/Test path. > No official publish/authentication tool is granted by this adapter. Triage alone > receives the optional dedicated bc-profiling and bc-snapshot proxies; discover > their schemas and confirm an authorized target/window before capture. Other > roles consume evidence. Capture does not prove autonomous snapshot debugging. > Symbol MCP: before any tools/call, verify AL CLI prerequisites are already > provisioned; this provider may auto-install AL tools on first use. A read-only > role must return that prerequisite to the caller, never bootstrap software. > Load symbols via al_packages(action: load, path: absolute consumer path). > The MCP process may run from the plugin cache; never assume its cwd is the > consumer. Use the discovered schema and report missing .app packages explicitly. > Record missing capabilities and unexecuted checks explicitly; never simulate.

AL Context File Generator

Generate a comprehensive `context.md` file that serves as the **master context document** for AI assistants and developers working on this AL/Business Central project.

Purpose

The `context.md` file provides:

• **Project Overview**: What this extension does and its business purpose
• **Architecture Snapshot**: How the code is organized and key patterns used
• **Critical Decisions**: Important architectural choices and their rationale
• **Integration Points**: Dependencies, events, APIs exposed/consumed
• **Quick Navigation**: Where to find specific functionality

This enables AI assistants to load complete project context quickly and make informed suggestions.

Execution Steps

1. Analyze Project Structure

**Load project metadata:**

# Get app.json configuration
@read_file app.json

# Understand dependencies
official AL MCP dependency query when granted, or manifest/symbol inspection

# Map directory structure
@list_dir src/

**Identify key patterns:**

# Find all table extensions
@search "tableextension" *.al

# Find all page extensions
@search "pageextension" *.al

# Find event subscribers
@search "EventSubscriber" *.al

# Find published integration events
@search "IntegrationEvent" *.al

# Find API pages
@search "APIPublisher\|APIVersion" *.al

2. Analyze Business Domain

**Understand what the extension does:**

• Read README.md if exists
• Analyze table/page names to understand business entities
• Check codeunit names for business processes
• Review comments and XML docs for business rules

**Key questions to answer:**

• What business problem does this solve?
• Who are the end users?
• What standard BC functionality does it extend?
• What industry/vertical is this for (if applicable)?

3. Document Architecture Patterns

**Identify and document:**

• **Organization Strategy**: Feature-based vs object-type folders?
• **Naming Conventions**: Prefixes, suffixes, patterns used
• **Extension Patterns**: How are standard objects extended?
• **Event Usage**: Subscriber patterns, custom events published
• **Data Model**: Key tables and their relationships
• **Processing Logic**: Main codeunits and their responsibilities
• **UI Structure**: Page organization and user flows

4. Map Integration Points

**Document:**

• **Dependencies**: What other extensions are requi