al-implement

Drives AL tasks red to green through TDD for Business Central.

4|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/FBakkensen/bc-agentic-dev-tools-marketplace --skill al-implement-fbakkensen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: al-implement
Source: https://github.com/FBakkensen/bc-agentic-dev-tools-marketplace/tree/main/plugins/al-agentic-dev/skills/al-implement
Command: npx skills add https://github.com/FBakkensen/bc-agentic-dev-tools-marketplace --skill al-implement-fbakkensen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Implementing Business Central AL features without a disciplined test-first workflow leads to untested code, drifting specs, and unclear task status. This Skill picks a ready-for-implementation task and drives it red to green through TDD, one AAA case at a time. ## Core Features & Use Cases - Task-driven TDD: Picks the next ready-for-implementation technical task from the tasks/ folder and drives Unit then Integration AAA cases red to green via per-case subagents. - Push-up gating: Blocks silent test-layer escalation by requiring an explicit commitment before writing tests above the blessed scope. - Spec reconciliation: Reconciles procedure names, object surfaces, and contract notes in the task file before flipping status to done, then opens unblocked dependent tasks. - Use Case: After running /al-refine on a task, invoke this Skill to implement the feature test-first, compile and test via /al-build, and hand off to /al-refactor and /al-mutate once the suite is green. ## Quick Start Run /al-implement to pick the next ready-for-implementation task and drive it red to green through TDD.

Frequently Asked Questions about al-implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement an AL task with TDD in Business Central?

Run /al-implement after /al-refine has filled the task's Test Specification. It drives Unit AAA cases first, then Integration cases, each red to green via a spawned subagent, and flips the task status to done once the full suite is green.

What task status is required before running al-implement?

The task must have status ready-for-implementation with a populated Test Specification. A plain ready status routes to /al-refine, while blocked or missing specs route to /al-steer for resolution first.

Can al-implement write Integration tests instead of Unit tests?

Only through a push-up commitment gate. If a Unit case cannot hold, the Skill stops and requires an explicit decision to build a seam or accept the slower Integration test, recording the justification in Contract notes.

What happens after a task reaches done in al-implement?

The Skill reconciles the task spec to the actual diff, commits the work, opens same-slice dependent tasks whose depends_on is satisfied, and hands off to /al-refactor then /al-mutate for non-trivial work.

When does al-implement stop and route to al-steer?

It stops when a replan trigger fires, such as hidden prerequisites, wrong task order, architecture decomposition errors, or goal drift. The task flips to blocked with a one-line blocked-on headline for /al-steer to resolve.