bc-al-project-context

Manage AL development context with decision records and session handoffs.

20|5|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/fernandoartalf/AL-Copilot-Skills-Collection --skill bc-al-project-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bc-al-project-context
Source: https://github.com/fernandoartalf/AL-Copilot-Skills-Collection/tree/main/skills/bc-al-project-context
Command: npx skills add https://github.com/fernandoartalf/AL-Copilot-Skills-Collection --skill bc-al-project-context

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the management of project knowledge by capturing and organizing architectural decisions and session progress, preventing loss of context in AL development workflows.

Core Features & Use Cases

  • Decision Documentation: Create, update, and query Architecture Decision Records (ADRs) to clarify why design choices are made.
  • Session Handoff Management: Generate and interpret session handoff documents to ensure seamless work transitions.
  • Use Case: When starting a new development session or onboarding a new developer, generate a comprehensive project context including recent decisions and current status to speed up familiarization.

Quick Start

Ask the AI to generate the latest project context report including recent decisions and handoffs.

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 AL development without losing track of decisions?

Automating AL project context management captures architectural decisions and session transitions in markdown templates and version-controlled metadata files, ensuring project history remains accessible and preventing context loss across development workflows.

What is the best way to generate a session handoff document for AL development?

Generating a session handoff document involves creating structured markdown files that capture current development progress and status, enabling seamless work transitions between team members during AL project sessions.

How do I create and query Architecture Decision Records for my AL project?

Creating Architecture Decision Records (ADRs) involves documenting design choices in structured markdown files, which can then be queried to clarify why specific architectural decisions were made throughout the AL development lifecycle.

Do I need version control to manage AL project documentation and decisions?

Managing AL project documentation requires version-controlled metadata files to ensure accurate and accessible project history, combining markdown templates with version control systems to maintain comprehensive architectural decision records.

Can I use markdown templates for onboarding new developers to an AL project?

Onboarding new developers to an AL project utilizes markdown templates to generate comprehensive project context reports, including recent architectural decisions and current session status, accelerating familiarization with the codebase.

Why does my AL development team keep losing context between sessions?

Losing context between AL development sessions happens when architectural decisions and progress are not systematically documented; automating session handoff management and decision tracking prevents this context loss.