ALDC¶
From business requirements to AL development.
Specialist AI agents. Human review. Design the architecture, define connected specifications, and coordinate implementation, testing and review for Business Central. You decide at key checkpoints.
Version 5.0.0 is available for VS Code from the Marketplace, and for Copilot CLI, Claude Code and Codex from the tagged source.
What is new in 5.0.0¶
-
Architect → Spec
Architect defines units, shared contracts and dependencies. Spec develops each contract and returns contradictions for joint review.
-
AL18 · Tools · MCP
Optional BC29-native guidance for AL tools available in Copilot Chat. BC28 remains the default; selecting a profile does not install tools or change app.json.
-
Doctor · BCQuality
Operation-specific diagnostics and optional BCQuality reviews. Configuration, discovery, loading and execution are recorded as separate facts.
-
Recoverable updates
Review collisions, verify installed content and restore the preceding transaction when integrity checks permit it. Restoration protects later edits.
-
Project Manager
One panel in VS Code, also available in the Explorer, to install, update, verify, restore and run Doctor for the selected project. Every change is previewed and confirmed; results stay in the panel.
-
ALDC Visor
Explorer tree of the plan artifacts per requirement: requisites, architecture, specification, test plan, phase reports and review evidence, each with its own icon. Read-only and always current.
From design to reviewable implementation¶
Architect determines how many specifications a solution needs, what they share and which can be drafted independently. Drafting and implementation dependencies are evaluated separately. Actual concurrency depends on the host and execution; a plan does not demonstrate that agents ran in parallel.
Spec develops technical contracts and acceptance criteria within the approved design. Joint review checks the current revisions before handoff to Conductor or Developer. Conductor coordinates planning, test-first implementation and review. Skills supply domain guidance when the task calls for it.
Explore Spec Agent · BC28 / BC29-native profiles
Reviews with BCQuality¶
BCQuality is optional and installed separately. Choose plugin or external-workspace mode in aldc.yaml, with the exact provider identity. Review evidence distinguishes discovery, loading, execution and index generation; native coverage is retained when external results are insufficient.
Your environment. Your starting point.¶
Choose where you work. Get the installation steps, checks and a first request for that surface.
GitHub Copilot
VS Code
→ From sourceGitHub Copilot
CLI
→ From sourceClaude Code
Plugin
→ From sourceCodex
Project setup
→The VSIX updates the VS Code extension. Each project toolkit and each terminal plugin has its own update step.
Resources¶
Everything ALDC-related lives here. Pick your path.
Getting Started
Install the toolkit and prepare your first requirement.
→ GuideCollection Guide
The public guide to ALDC: architecture, primitives, flow, validation and adoption.
→ RolesAgents
Architect, Spec, Developer, Conductor, Pre-Sales — plus on-demand Triage & Dredd. What each one does and when.
→ AutomationWorkflows
Workflows from initialization to PR preparation. Invocable from chat.
→ StandardsInstructions
Scoped AL coding instructions. Style, perf, naming, errors, events.
→ ExecutionComplete Development Flow
See the end-to-end path from requirement intake to validated delivery.
→ TalksEvents & Talks
Conference sessions, community talks and upcoming public appearances.
→ ExampleReproducible Example
Walk through a concrete ALDC setup with a documented starting point.
→ ContributeContributing
Open issues, submit improvements and propose new primitives with the repo guidelines.
→ Open sourceSource code
Every agent, skill and workflow. MIT licensed. Star and fork welcome.
→ CommunityDiscussions
Ask questions, share patterns and propose primitives with the community.
→ HistoryChangelog
Track releases, fixes and the evolution of the collection over time.
→Events & talks¶
ALDC also exists outside the repo: conference talks, Dev Days and hands-on sessions where the collection, workflow and delivery model are the topic. Here you only see confirmed upcoming talks.
How to collaborate¶
Four ways to make ALDC better. No contribution is too small.
Try it and tell me
Install, build something real, and open an issue with what broke, what felt awkward, or what you wish existed. Bug reports are gold.
Open an issue →Contribute a primitive
Have a skill, workflow or agent you'd pay for? Propose it. Fork, follow the contribution guide, open a PR.
Contribution guide →Shape v1.2
Priorities are discussed openly. Vote on trade-offs, challenge assumptions, and propose alternatives with the community.
Join the discussion →Share the workflow
Star the repo. Mention ALDC in your BC community, internal enablement docs or session notes. Useful references beat generic hype.
Star on GitHub →