FBakkensen

Build and test AL/Business Central projects. Use after modifying AL code or tests to verify the build gate passes. Runs compilation, publishing, and test execution in a single command. Required gate before committing AL changes.

AL/Business Central code review at gate points. Report-only by default; pass --fix to land must-fix findings and re-review once. Use when a slice's last technical task lands (slice-done) — both backend-only and user/API-facing slices, before the verify task is refined — when all tasks are done before merge (feature-done), or when the user asks for an in-depth code review.

Pick a `ready-for-implementation` technical task from the `tasks/` folder and drive it red→green through TDD for AL/Business Central. Use after `/al-refine`, one task per session, Unit AAA cases first, then Integration AAA cases. Stops at green and hands off to `/al-refactor` then `/al-mutate`.

Validate AL/Business Central test rigor by mutation: inject one mutation at a time, run the script-backed build gate, classify, revert, report killed/surviving/equivalent mutants. The rigor step the user runs after `/al-refactor` on whatever arrived without a red, or standalone on legacy code before `/al-refactor`.

Reshape AL/Business Central production and test code while tests stay green, via four parallel lens subagents then serial apply with `/al-build` between. Use after `/al-implement` takes a task to green (full task diff, once per task) or standalone on legacy code.

Settle the AL/Business Central feature architecture from idea or `event-model.md`. Use after `/al-event-model` for user/API-facing features, after `/al-grill-adr` for backend-only features, or when the user asks to design an AL feature.

Domain-aware grilling for AL/Business Central. Sharpens BC vocabulary against CONTEXT.md, cross-references intent with the codebase, and offers domain ADRs only when a hard-to-reverse business rule earns one.

One `status: ready` task to a fresh Test Specification or Verification Plan for AL/Business Central. Technical task -> ready-for-implementation. Verify task -> ready-for-verification.

Implement the next unblocked backlog task for the current project by reading `tasks.md`, selecting the first eligible `Status: [ ]` item, interviewing the user with the `grill-me` flow, presenting an approval checkpoint, and then implementing and verifying the task under the repo's engineering principles. Use when Codex should drive backlog execution for this repository instead of handling a one-off coding request.

Write a professional blog post for the Jekyll blog. Use when drafting new blog posts, writing technical articles, or creating content. Applies copywriting best practices (AIDA, PAS, Inverted Pyramid, etc.) to produce publication-ready drafts. Use this skill whenever the user mentions writing a blog post, drafting an article, creating content for the blog, or wants to turn notes/ideas into a published post.