/aldc

name: aldc
description: Use canonical ALDC architecture, implementation, TDD orchestration, review and specification workflows for AL / Business Central projects.

Read the relevant role or workflow below in full before acting. Resolve these links from this skill directory, including when a plugin cache holds it. For AL tools, first read [AL tooling](references/al-tooling.md): it separates MCP operation scope from the unresolved native LSP route. Reading this skill does not apply custom-agent TOML permissions. Load applicable rules from references/rules/ and domain guidance from references/skills/ (GUIDE.md) on demand. These domain references are not duplicate discoverable skills. Recover approved work from .agents/plans/ and memory.md.

For MEDIUM/HIGH work, preserve architecture → specification → Conductor order. The al-spec-create workflow loads the same al-spec-agent contract as direct role invocation. Human material gates and current session authorization govern actions. Plugin installation alone does not authorize compilation, publishing or deployment.

Use discovered project custom agents when available. Otherwise read the selected role as instructions in this session; when independent subagents are required and unavailable, report the affected step as pending. Do not invent a tool name or claim independent review from a sequential role change.

Roles

• [al-agent-builder](references/agents/al-agent-builder.md): Agent Toolkit Builder — specialist in designing and coding Business Central agents using the AI Development Toolkit and Agent SDK. Follows the official Agent Template project structure. Handles both Designer (no-code) and SDK (pro-code) paths. Use when building BC agents or agent SDK integrations.
• [al-architect](references/agents/al-architect.md): AL Architecture and Design assistant for Business Central extensions. Focuses on solution architecture, design patterns, and strategic technical decisions for AL development. Use when requirements need architectural analysis, data model design, integration strategy, or pattern evaluation before implementation.
• [al-conductor](references/agents/al-conductor.md): AL Conductor Agent - Orchestrates Planning → Implementation → Review → Commit cycle for AL Development. Enforces TDD and quality gates for Business Central extensions. Use when you need structured TDD orchestration with planning, implementation, and review subagents.
• [al-developer-reviewer](references/agents/al-developer-reviewer.md): Independent read-only review of an AL increment implemented directly by Developer, without Conductor. Checks acceptance, BCQuality and current validation evidence before human approval.
• [al-developer](references/agents/al-developer.md): AL Developer - Tactical implementation specialist for Business Central extensions. Edits AL, builds via the terminal, and validates with tests. Implements features following specifications without making architectural decisions. Use when you need to implement, code, debug, or fix AL code directly.
• [al-implement-subagent](references/agents/al-implement-subagent.md): TDD Implementation Subagent — Creates AL objects following strict RED→GREEN→REFACTOR cycle. Only invokable by al-conductor via the available native subagent tool.
• [al-planning-subagent](references/agents/al-planning-subagent.md): AL Planning Subagent - AL-aware research and context gathering for Business Central development. Returns structured findings to Conductor for plan creation.
• [al-presales](references/agents/al-presales.md): Technical PreSales Agent for AL/Business Central projects. Specializes in project planning, cost estimation (time & budget), feasibility analysis, SWOT/risk assessment, and technical documentation. Orchestrates AL Architecture & Design Specialist and al-spec-create for comprehensive proposals. CREATES Technical_PreSales folder and documents dynamically on demand. Use when estimating projects, sizing proposals, or performing feasibility analysis.
• [al-review-subagent](references/agents/al-review-subagent.md): AL Code Review Subagent - Quality assurance for Business Central AL code. Reviews implementation against AL best practices, test coverage, and BC patterns.
• [al-spec-agent](references/agents/al-spec-agent.md): Turn an approved Business Central requirement and architecture into one implementable AL specification. Own technical contracts and acceptance criteria without writing AL implementation or changing architecture.
• [al-triage](references/agents/al-triage.md): Reactive support for EXISTING Business Central AL code — reproduce, localize, root-cause, and recommend a minimal fix for bugs, regressions, and incidents. Read-only on code: produces a diagnosis and hands the fix to al-developer. The dynamic counterpart to Dredd (static audit). Use when you start from a symptom ("this throws", "this is slow", "broke after the last change").
• [dredd](references/agents/dredd.md): Independent, on-demand AL codebase auditor for Business Central. Judges the code against BCQuality (citable knowledge) plus native checks for what BCQuality does not reach. Read-only; advisory verdict. Default scope: objects changed vs main; full codebase on request.

Workflows

• [al-spec-create](references/commands/al-spec-create.md): Create or revise the canonical AL technical specification through AL Spec Agent, preserving approved architecture and human approval. ALDC workflow (Copilot prompt al-spec-create); invoke explicitly.
• [al-build](references/commands/al-build.md): Build, package, and deploy AL extensions to Business Central environments. ALDC workflow (Copilot prompt al-build); invoke explicitly.
• [al-pr-prepare](references/commands/al-pr-prepare.md): Prepare a clean, documented pull request draft for AL features or fixes with summary, testing notes, and checklist. ALDC workflow (Copilot prompt al-pr-prepare); invoke explicitly.
• [al-memory-create](references/commands/al-memory-create.md): Generate or up