al-scope

Decomposes architecture.md into slice-grouped task files for AL/Business Central development.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a Business Central architecture document into an executable, dependency-ordered task list is error-prone when done by hand. This Skill converts architecture.md (and event-model.md when present) into a structured tasks/ folder with per-task files, dependency edges, and verification gates so downstream skills can refine and implement one task at a time. ## Core Features & Use Cases - Slice-grouped decomposition: Generates one task file per behaviour slice, grouped by event-model timeline steps or architecture slices, with a 000-feature.md header carrying the feature goal. - Dependency graph in frontmatter: Each task carries depends_on, refactors, and fixes edges plus status, slice, and kind fields, forming a machine-readable execution graph with gapped ordering prefixes. - Verify and ops tasks: Emits a user sign-off verify task per user-facing slice and bracketing provision/breaking-change ops tasks, then runs a document-integrity check before handing off. - Use Case: After running /al-design on a sales order feature, invoke this Skill to produce tasks/ files such as 010-T-001-provision.md and per-slice technical tasks, then greenlight /al-provision T-001 to start implementation. ## Quick Start Run /al-scope after /al-design to decompose the architecture document into the tasks folder for the current feature branch.

Frequently Asked Questions about al-scope

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

FAQPage Schema
How do I turn an architecture document into a task list for Business Central development?

Run /al-scope after /al-design has produced architecture.md. It writes a tasks/ folder with a 000-feature.md header and one file per task, grouped by slice with dependency edges, ready for /al-provision and /al-refine.

What is the difference between technical, verify, provision, and breaking-change tasks?

Technical tasks carry implementation context and route through /al-refine to /al-implement. Verify tasks capture user sign-off per slice, while provision and breaking-change are ops tasks that bypass refinement and run directly.

Does al-scope work for backend-only features without an event model?

Yes. Backend-only features use architecture.md alone, with slices taken from its slice declarations. No verify tasks are emitted since there is no user-facing surface, and cross-slice dependencies target the prior slice's last technical task.

What happens if the architecture document has gaps during decomposition?

The Skill stops and routes to /al-steer instead of inventing missing details. Unanswerable questions, missing modules, or slices absent from event-model.md block the write to prevent corrupting downstream skills.

Why does al-scope not write test specifications or verification plans?

Task files carry context only, not proof artifacts. /al-refine owns and freshly writes Test Specifications, Verification Plans, and Decision Matrices per task, so pre-writing them in scope would duplicate or stale that work.