mirror of
https://github.com/microsoft/BCQuality.git
synced 2026-08-06 09:26:52 +01:00
2401443ef8
Turn the object-granularity al-object-author super-skill into the feature/PR-level al-feature-author - the true authoring counterpart of al-code-review, which takes a whole PR. feature-spec in -> whole-PR code-artifact out. - microsoft/skills/author/al-feature-author.md (renamed from al-object-author.md): takes inputs [feature-spec]; decomposes it into a cross-referenced object graph, allocates a contiguous object-ID block, applies the mandatory affix, resolves cross-object references (API page SourceTable = authored master), fans each derived object-spec out to the worklisted leaves, rolls up their artifacts, reconciles the refs, and enumerates the objects no current leaf authors (List/Card pages, permission set, install codeunit) as open-questions. Worked example: a Membership feature -> 3 artifacts (master table + setup table from al-table-author, API page from al-api-page-author) rolling up to completed. - skills/do.md (composition v1.1, STABLE-CONTRACT): add feature-spec to the standard inputs; extend Relevance so a super-skill's inputs need not equal its leaves' - it may derive the leaves' inputs by decomposing its own; generalize Action rollup to findings-report OR code-artifact. Review (findings) semantics read identically - behavior-preserving. - .github/scripts/validate_frontmatter.py: add feature-spec to STANDARD_INPUTS. #67 R26 generalization unchanged. - README.md, agent-consumption.md: author family's top-level skill is now al-feature-author. The al-table-author leaf and the R26 generalization from #67 are unchanged. Knowledge article count unchanged at 199. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| do.md | ||
| entry.md | ||
| read.md | ||
| README.md | ||
| write.md | ||
BCQuality global skills
This folder contains the skills that are not owned by any single layer. There are two kinds:
- The entry-point skill — the first skill an agent invokes at runtime.
- The three meta-skill contracts — stable references that define what the rest of BCQuality means.
The entry-point skill
| File | Role |
|---|---|
entry.md |
ENTRY — Given a task context, returns a dispatch record naming the action skill(s) to invoke. The agent's first call when pointed at BCQuality. |
Routing logic lives in Entry, not in the orchestrator. An agent that knows only "invoke /skills/entry.md first" has enough to drive the rest of the repo.
The meta-skill contracts
| # | File | Role | Who reads it |
|---|---|---|---|
| 1 | read.md |
READ — Schema + Use. How to read a knowledge file: frontmatter fields, section semantics, matching rules, layer precedence, conflict resolution. | Any agent or action skill that consumes knowledge files. |
| 2 | do.md |
DO — Action Skill contract. The Source → Relevance → Worklist → Action template and the structured output every action skill produces. Includes super-skill composition. | Any agent invoking an action skill; every action-skill author. |
| 3 | write.md |
WRITE — New Knowledge. Authoring rules for knowledge files. Defers to read.md for the schema. |
Contributors (human or agent) adding or editing knowledge files. Not used during consumption. |
READ and DO are read on demand — typically by the first action skill the agent executes after dispatch. They are not prerequisites for invoking Entry. WRITE is only used when scaffolding new content.
These contracts are stable. Changes require a PR approved by both maintainers.
For the end-to-end flow — from orchestrator trigger through to findings integration — see ../agent-consumption.md. For the high-level project framing, see ../README.md.