mirror of
https://github.com/microsoft/BCQuality.git
synced 2026-08-06 09:26:52 +01:00
Authoring pilot: al-api-page-author skill + code-artifact output kind
Add the first authoring action skill (al-api-page-author) and extend the stable DO contract with a second output kind (code-artifact) plus the object-spec input. Reuses existing web-services API knowledge with no new knowledge articles; article count unchanged. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
parent
24e62f5ec8
commit
57f4c0602c
5 changed files with 212 additions and 3 deletions
|
|
@ -71,6 +71,8 @@ The output contract is defined in the DO meta-skill so that every action skill
|
|||
|
||||
The orchestrator parses this **without skill-specific logic**. This is the point of the contract: orchestrators and action skills evolve independently.
|
||||
|
||||
> **Authoring skills.** The same four-step pattern also drives *authoring* skills, which generate code rather than review it. They consume an `object-spec` and emit a `code-artifact` (the full generated AL as an escaped string, with per-artifact `references`, `notes`, and task-level `open-questions`) instead of a findings-report. The orchestrator maps each artifact to **file creation or scaffolding** in the target repo rather than to PR comments or build gates. The first example is `microsoft/skills/author/al-api-page-author.md`; the `code-artifact` contract is defined in [`skills/do.md`](skills/do.md).
|
||||
|
||||
### 7. Orchestrator integrates
|
||||
The orchestrator turns findings into PR comments, build gates, or IDE diagnostics, and links the references back to the knowledge files so the PR author — human or agent — can read the guidance.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue