Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-10-05 06:36:55 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Narrow development guidance to provisional contract

Browse source 
Keep plan enrichment internal and read-only pending consumer agreement and runtime pilot evidence. Move knowledge to its independent PR and remove the consumer-owned forensic evaluator.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 638b66d2-9f06-4f60-8781-808709e1485c
This commit is contained in:
Jesper Schulz-Wedde 2026-09-18 15:46:52 +02:00
parent 8f025ac679
commit fa7eb750c6
40 changed files with 294 additions and 2053 deletions
Download patch file Download diff file Expand all files Collapse all files

41
README.md
View file

@ -26,34 +26,24 @@ copilot plugin install microsoft/BCQuality
copilot plugin list
```
The list should include `bcquality`. The plugin exposes
[`al-code-review`](skills/al-code-review/SKILL.md) and the read-only
[`al-development-plan`](skills/al-development-plan/SKILL.md) plan-enrichment
skill. Installation and skill discovery are the general pattern; reviewing an
app is one example of using it.
The list should include `bcquality`. The plugin exposes the
[`al-code-review`](skills/al-code-review/SKILL.md) skill. Installation and skill
discovery are the general pattern; reviewing an app is one example of using it.
Plugin version `0.3.0` adds `al-development-plan`, a read-only adapter for
enriching an **existing** plan. It does not generate a plan or implement code.
The adapters are intentionally not second implementations:
The adapter is intentionally not a second implementation:
```text
standalone host skill: skills/al-code-review/SKILL.md
-> routing contract: skills/entry.md
-> review coordinator: microsoft/skills/review/al-code-review.md
-> domain review leaves
standalone host skill: skills/al-development-plan/SKILL.md
-> routing contract: skills/entry.md
-> enrichment skill: microsoft/skills/development/al-development-plan.md
-> referenced constraints for the consumer's existing workflow (read-only)
```
Only the files under `skills/*/SKILL.md` follow the host's packaging format.
The remaining files are BCQuality's internal protocol and layered action
skills. Entry remains the single owner of routing and index preparation. This
separation keeps standalone installation available without duplicating policy
in either adapter.
in the adapter.
### Example: Review a complete app folder
@ -73,7 +63,7 @@ Approve access only to a project you trust, then ask:
The folder should contain `app.json` and your AL source; it does **not** need
to be a Git repository. On macOS or Linux, use your app's local path instead.
Each host adapter and internal action skill intentionally share a name: they
The host adapter and internal action skill intentionally share a name: they
expose the same operation in two different skill formats. Their paths make the
boundary explicit.
@ -111,8 +101,11 @@ available domains and the difference between a folder review and a comparison.
Mechanical issues already enforced by the AL compiler or standard analyzers are
intentionally left to those deterministic tools rather than duplicated here.
The read-only `al-development-plan` interface selects relevant constraints
before the consumer implements its own existing plan.
BCQuality defines a provisional internal, read-only `al-development-plan`
action-skill contract that selects relevant constraints before a consumer
implements its own existing plan. It is not registered as a standalone plugin
skill and does not change the plugin version. Consumer-owner agreement and a
runtime pilot are required before treating it as a stable public surface.
Repository-specific orchestrators retain planning, implementation, approvals,
tests, environment, propagation, and delivery ownership. The intended flow is
@ -131,14 +124,12 @@ Functional areas such as Finance, Supply Chain Management, Manufacturing, Jobs,
Warehousing, and Service, and technologies such as PowerShell, pipelines, and
Power Platform, remain valid future scope, **not current coverage claims**.
## Evidence and follow-up scope
## Plan-enrichment follow-up scope
The [guidance evaluation](evaluation/README.md#read-only-plan-guidance) separates
credential-free contract/scorer regressions from external agent and runtime
evidence. Prepared requests and fixture counts do not establish compilation,
test execution, better repairs, or a capability percentage. Consumer adoption,
a pinned baseline comparison and runtime pilot, standalone authoring, and
source-ingestion catalog work remain separate follow-ups.
Consumer agreement, consumer-owned persistence and phase injection, a pinned
baseline comparison, and a runtime pilot remain follow-up work. BCQuality does
not claim improved repairs or authoring effectiveness from this provisional
contract alone.
## What's in this repo