[Epic] Roadmap: complete BCQuality — the one-stop shop for Business Central development #83

Vision

Make BCQuality the one-stop shop for Business Central development — a knowledge base + skills layer complete enough that even cheap/fast models can both develop and review BC apps. The review half is mature; the authoring half is being built. This epic tracks the remaining work to complete both, organized by two goals.

Legend: ✅ merged · 🔄 in flight (open PR) · ⬜ planned (issue)

---

Goal 1 — Complete the knowledge base

Scope follows README §Scope (functional domains, AL language, PowerShell, pipelines, BC APIs, Power Platform, telemetry/KQL, AppSource).

• Add the "develop" half: generation output contract, scaffolding skills, golden templates, and anti-hallucination reference #34 — the "develop" half: generation output contract, scaffolding skills, golden templates, anti-hallucination platform reference (foundational)
• Add BC functional-domain knowledge and a standard application-object reference #35 — BC functional-domain knowledge + standard application-object reference · pilot 🔄 Add source-verified Finance knowledge and review domain #57
• Add AppSource lifecycle knowledge + a unified analyzer/compiler rule index #36 — AppSource lifecycle + unified analyzer/compiler rule index
• Add a telemetry domain (signal emission + KQL), distinct from the privacy rules #37 — Telemetry domain (signal emission + KQL)
• Add pipeline/automation knowledge: PowerShell (BcContainerHelper) and AL-Go for GitHub #38 — PowerShell (BcContainerHelper) + AL-Go pipelines
• Expand the testing domain (currently 1 file) into full AL test-authoring knowledge + test skills #39 — Testing domain (knowledge half)
• Add Power Platform integration knowledge domain #69 — Power Platform integration
• ✅ Baseline merged: seeded domains — error-handling, events, interfaces, web-services, breaking-changes, performance, privacy, security, style, ui, upgrade, testing (+ appsource, data-modeling 🔄 Add data-modeling and appsource knowledge articles (MICROSOFT layer) #65). Deepen seeded domains as gaps surface.

Goal 2 — Complete the review & coding skills

Foundation

• 🔄 Authoring pilot: al-api-page-author skill + code-artifact output kind #61 — generation output contract (code-artifact) + first author leaf (al-api-page-author)
• 🔄 Add al-table-author leaf + al-code-author super-skill (role-level authoring, counterpart to al-code-review) #67 — al-table-author leaf + al-code-author super-skill (role-level authoring counterpart to al-code-review)

Review skills — one al-*-review leaf per domain

• Tracking: complete review-leaf coverage (one al-*-review per domain) #81 — review-leaf coverage tracker → ⬜ Add al-appsource-review leaf (wire into al-code-review) #70 (appsource) · ⬜ Add al-data-modeling-review leaf (wire into al-code-review) #72 (data-modeling) · ⬜ Expand the testing domain (currently 1 file) into full AL test-authoring knowledge + test skills #39 (testing)

Coding skills — one al-*-author leaf per object type

• Tracking: complete author-leaf coverage (one al-*-author per BC object type) #82 — author-leaf coverage tracker → ⬜ Add al-page-author leaf (List/Card pages; wire into al-code-author) #71 Add al-table-extension-author leaf (wire into al-code-author) #73 Add al-install-codeunit-author leaf (wire into al-code-author) #74 Add al-permission-set-author leaf (wire into al-code-author) #75 Add al-page-extension-author leaf (wire into al-code-author) #76 Add al-codeunit-author leaf (event subscribers; wire into al-code-author) #77 Add al-upgrade-codeunit-author leaf (wire into al-code-author) #78 Add al-report-author leaf (wire into al-code-author) #79 Add al-interface-author leaf (wire into al-code-author) #80
• al-code-author: graduate beyond greenfield — author changes to existing code (bug fixes / refactors) #68 — beyond greenfield: author changes to existing code (bug fixes / refactors)
• Expand the testing domain (currently 1 file) into full AL test-authoring knowledge + test skills #39 — test-authoring skill (al-test-generate)

---

Cross-cutting / governance

• Stable-contract changes to skills/do.md (output kinds, composition) and the validator (e.g. R26) require maintainer approval — flag them in the PR body.
• Knowledge is layered (microsoft/ authoritative, community/ incubating) with domain-expert CODEOWNERS gates.
• Skills are not knowledge — the knowledge-index count only moves when articles change.

In-flight PRs (awaiting review; keep as-is)

#61 · #62 · #65 · #67 (+ #49, #54, #57). Where stacked, merge order is #61 → #65 → #67.