al-refine

Generates Test Specifications and Verification Plans for AL/Business Central tasks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AL/Business Central development tasks often reach implementation with vague or stale proof plans, forcing developers to re-derive intent mid-TDD. This Skill regenerates a fresh, grounded Test Specification or Verification Plan for one ready task so implementation and verification proceed without ambiguity. ## Core Features & Use Cases - Test Specification generation: Rewrites the proof section of a kind: technical task with AAA cases, coverage IDs, decision matrices, and New/Modified object signatures, then flips status to ready-for-implementation. - Verification Plan generation: For kind: verify tasks, authors E2E journey examples, contract examples, and exploration charters tied to the event model, then flips status to ready-for-verification. - Grounding and gating: Verifies every BC symbol against workspace evidence, runs a document-integrity check, detects push-up tests, and routes unanswerable tasks to research, grilling, or replanning skills. - Use Case: After scoping a feature into tasks, run the refine step on task T-012 to produce a grounded Test Specification that the implementation skill drives red-to-green without re-deriving intent. ## Quick Start Refine task T-012 into a fresh Test Specification so it is ready for implementation.

Frequently Asked Questions about al-refine

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

FAQPage Schema
How do I turn a scoped AL task into a Test Specification?

Run the refine step on one named task with status ready. It regenerates the proof section from current app code and tests, grounds every symbol, writes AAA cases with coverage IDs, and flips the task to ready-for-implementation.

What is the difference between a Test Specification and a Verification Plan?

A Test Specification proves a technical task's behaviour through Unit and Integration AL tests. A Verification Plan checks a slice through its user or API surface using E2E journeys, contract examples, and exploration charters.

Can I refine a provision or breaking-change task?

No. Provision and breaking-change tasks are not refine targets because they carry no proof artifact. They stay at status ready and route to the provisioning or breaking-change validation skills instead.

Why does refine stop and route to al-steer on some tasks?

Refine stops when preconditions fail: missing architecture or event-model files, unsatisfied dependencies, a replan flag, or a deferred question the task touches. Routing to al-steer prevents writing specs that encode guesses or skip review gates.

When should an E2E journey be marked Record: yes?

Mark Record: yes only when no AL test layer can automate the behaviour, such as control add-ins or web-client-only behaviour. Behaviour a Unit or Integration test can pin stays Record: no and is walked for acceptance without recording.