al-grill-adr

Interviews users to resolve Business Central domain terminology and records decisions in CONTEXT.md and ADRs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AL/Business Central features often start with ambiguous domain vocabulary and hidden trade-offs that surface as bugs during implementation. This Skill interviews the user one question at a time, cross-references intent against the codebase, and crystallizes decisions into CONTEXT.md and domain ADRs before any code is written. ## Core Features & Use Cases - Domain grilling: Asks one focused question at a time with lettered options, reading the codebase when code can answer and asking the user only what code cannot tell. - CONTEXT.md and ADR authoring: Writes canonical BC terminology to CONTEXT.md and offers domain ADRs only when a constraint is hard to reverse, surprising, a real trade-off, and business-level. - Deferred-question ledger: Records undecidable questions under .not-yet-specified/ so they survive the session instead of becoming guesses at implementation time. - Use Case: Before designing a partial-posting feature, run the grill to pin down what "posting" means in this project, expose conflicts with existing code, and capture the resulting business rule as an ADR. ## Quick Start Ask the assistant to grill you on the domain intent of your new Business Central feature before any design or implementation begins.

Frequently Asked Questions about al-grill-adr

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

FAQPage Schema
How do I clarify Business Central domain terminology before writing AL code?

Run a domain grilling session that asks one question at a time, resolves each ambiguous BC term to a canonical name, and records the result in CONTEXT.md. Terms the workspace cannot settle are routed through research before being written.

When should I write an architecture decision record for a Business Central feature?

Write a domain ADR only when all four conditions hold: the constraint is hard to reverse, surprising without context, a real trade-off with genuine alternatives, and a business rule rather than a code-shape decision. Three of four does not earn one.

What files does the al-grill-adr skill write to?

It writes only CONTEXT.md at the repo root, accepted domain ADRs under docs/adr/, and deferred questions under .not-yet-specified/. It never edits implementation, test, or application code, and never writes event-model.md, architecture.md, or task files.

What happens to questions that cannot be answered during a grilling session?

Questions the user says matter but cannot yet decide are written as files under .not-yet-specified/ describing the question and what it waits on. This keeps them visible for later grooming instead of resurfacing as guesses during implementation.

Does the grilling skill verify Business Central facts itself?

No. BC-specific terms that the workspace cannot settle are routed through the research skill, which is mandatory for durable artifacts. If research fails, the term or ADR is not written that session and grilling continues.