helfen-industries/al-development-workflow
Structured Business Central AL development workflows for GitHub Copilot
Create or update Business Central AL test-scenario documents from the authoritative User Story and keep scenario IDs, titles, Given/When/Then steps, and AL test comments synchronized. Use when documenting test cases from an assigned Task, deriving scenarios from acceptance criteria, or repairing test-documentation drift.
Run, diagnose, and fix Business Central AL automated tests in a strict red-green-refactor loop using VS Code test discovery and Test Results evidence. Use when implementing a documented scenario, repairing failing AL tests, validating a feature suite, or proving a test app is green.
Use AL Symbols MCP tools reliably for Business Central object, procedure, field, reference, and package searches, and route each question between AL Symbols, BC Observatory, BC Code Atlas, and Microsoft Learn. Always apply before AL symbol queries, when recovering from an empty package index, and before querying Microsoft object facts, base-app procedure bodies, version changes, or localizations.
Review a completed AL implementation before pull-request creation, then apply focused simplifications that improve readability and maintainability without changing intended behavior. Use after implementation and tests, or when asked to simplify, clean up, reduce AI slop, or prepare AL code for review.
Audit an AL repository or selected subsystem for readability, maintainability, unnecessary complexity, duplication, and AI slop. Use for repository-wide simplification reviews, technical-debt discovery, or selecting cleanup work before implementation.
Record the developer's active hours for a delivered Business Central work package, compare them with its estimate per category, write actuals.md beside the spec, and upsert one record in the user-level calibration log that workflow-spec-estimate reads. Use after workflow-pull-request-create creates a PR, or when the user asks to record, add, or correct actual effort for a plan.
Create one Azure Repos pull request from a fully prepared and explicitly confirmed request. Use only as the Azure DevOps provider adapter for workflow-pull-request-create after documentation, branch, push, title, description, target, and draft state are settled.
Retrieve an Azure DevOps work item and its implementation-relevant context through the external ado-remote-mcp server. Use for Azure DevOps URLs, work item IDs explicitly identified as Azure DevOps, ADO tickets, backlog items, bugs, tasks, or user stories.
Explore the current workspace read-only to find the AL objects, symbols, tests, conventions, and controlling code paths relevant to a work package. Use after requirements analysis and before clarification or implementation planning.
Review a completed Business Central AL implementation before pull-request creation. Run focused simplification, perform a findings-first whole-change review against the canonical spec, repair unambiguous defects, and prove tests and build remain green. Use after implementation or when preparing an AL change for pull request.
Create or update customer-facing documentation for an implemented Business Central feature from the canonical spec and verified final implementation. Use during pull-request preparation when customers need a non-technical explanation of what is new, how to set it up, how to use it, and any upgrade or limitation notes.
Grill the user about implementation decisions until every reachable branch is resolved and shared understanding is confirmed. Use when requirements, behavior, interfaces, compatibility, or acceptance criteria still depend on human decisions.
Retrieve a GitHub issue and its implementation-relevant context using read-only tools. Use for GitHub issue URLs, owner/repository#number references, or requests to begin work from a GitHub issue.
Create one GitHub pull request from a fully prepared and explicitly confirmed request. Use only as the GitHub provider adapter for workflow-pull-request-create after documentation, branch, push, title, body, base, and draft state are settled.
Prepare documentation and create a pull request for a reviewed Business Central AL implementation. Synchronize implemented test scenarios, create non-technical customer documentation, build the PR description, route the confirmed write to GitHub or Azure Repos from repository context, and then capture the developer's active time for estimate calibration. Use only after workflow-code-review ends Ready for pull request.
Create the canonical implementation-ready Business Central AL technical specification from clarified requirements and verified workspace evidence, structured as a reviewer-readable concept, an object-centric technical design with a complete Object catalog, and an evidence appendix. Use only after critical decisions are resolved and relevant AL code has been explored, including when a change request updates an existing spec or needs a delta spec for an implemented one.
Estimate a ready Business Central technical specification as active human effort for AI-assisted delivery. Classify implementation items, test batches, and a delivery allowance, derive Best, Expected, and Worst from named conditions, calibrate start values with measured actuals, and keep agent runtime and fixed-price risk separate. Use only when explicitly asked to estimate a canonical spec.
Create the configured work-item branch and implement a ready canonical Business Central AL technical specification in dependency order with object-ID reservation, focused tests, and incremental validation. Use only when explicitly asked to implement an approved spec.
Analyze a normalized Business Central AL work package, separate verified requirements from assumptions, and identify acceptance criteria, dependencies, risks, and open implementation decisions. Use during work-package intake before code exploration or planning.
Start and orchestrate a Business Central AL work package from a direct requirement, Azure DevOps work item, or GitHub issue. Use whenever the user asks to begin a work package, provides requirements and acceptance criteria, or supplies a ticket, task, work item, or issue reference for specification.
Turn unresolved implementation decisions in an AL work package into a small set of precise questions and prevent planning from proceeding on invented defaults. Use after requirements and code exploration expose ambiguity or missing decisions.
Set up or validate repository defaults for the AL development workflow, including work-item retrieval, implementation branch naming, and pull-request routing. Use when the user asks for "AL workflow setup", asks to configure work-package context, or when work-package, implementation, or pull-request context is missing or incomplete.