bc-al-project-context

Document architectural decisions and session state for Business Central AL extensions.

1|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/javiarmesto/aldc-workshop-starters --skill bc-al-project-context-javiarmesto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bc-al-project-context
Source: https://github.com/javiarmesto/aldc-workshop-starters/tree/main/04-greenfield-starter/.github/skills/bc-al-project-context
Command: npx skills add https://github.com/javiarmesto/aldc-workshop-starters --skill bc-al-project-context-javiarmesto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents valuable Business Central AL project knowledge from being lost between coding sessions, developers, and AI agents by maintaining structured records of technical decisions and current project state.

Core Features & Use Cases

  • Architecture Decision Records: Create, update, and query ADRs that capture why significant AL extension design choices were made, including alternatives and tradeoffs.
  • Session Handoffs: Generate and read action-oriented handoff documents that preserve progress, next steps, blockers, and context across sessions.
  • Use Case: A Business Central development team can use this Skill when onboarding a new developer, resuming work after a break, or transferring an extension task to an AI coding agent.

Quick Start

Use the bc-al-project-context skill to create a handoff document summarizing the current Business Central extension development status and next action.

Frequently Asked Questions about bc-al-project-context

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

FAQPage Schema
How do I maintain project context for Business Central AL extensions across coding sessions?

Maintain AL project context by documenting architectural decisions and development session state. This Skill generates structured ADR and handoff documents in version-controlled markdown to preserve technical decisions and current progress.

What's the best way to document architectural decisions in AL development?

Document architectural decisions by creating Architecture Decision Records. These structured markdown files capture why significant Business Central extension design choices were made, including evaluated alternatives and technical tradeoffs.

Can I use session handoff documents to onboard AI coding agents for Business Central development?

Yes, you can use action-oriented session handoff documents to onboard AI coding agents. These records transfer Business Central extension tasks by preserving progress, next steps, blockers, and context across sessions.

How do I generate a development session handoff document for an AL extension project?

Generate a development session handoff document by summarizing the current Business Central extension development status and next action. The output is an action-oriented markdown record preserving progress and blockers.

When do I need formal project context tracking for Business Central development?

You need project context tracking when onboarding new developers, resuming work after a break, or transferring extension tasks to AI agents. This prevents valuable Business Central AL project knowledge from being lost.