Naming/framing change only - the authoring counterpart to al-code-review is
now the role-level al-code-author. The Action/Output substance is unchanged:
the decompose -> per-object fan-out -> roll up -> reconcile logic and the
Membership worked example stay exactly as they were and correctly describe the
skill's current mode (greenfield feature authoring).
- git mv al-feature-author.md -> al-code-author.md; id al-code-author,
title "AL code author", reframed description. Intro now states the role
(authoring counterpart to al-code-review, produces a whole PR of code) and
is honest that greenfield feature authoring is its first and currently only
mode (other modes such as defect-fix-from-bug-report are future extensions).
inputs [feature-spec], outputs [code-artifact], sub-skills [al-api-page-author,
al-table-author] and dimension fields all unchanged.
- skills/do.md: one-word consistency tweak in the Composition Relevance example
(a feature author -> a code author). Behavior-preserving; the findings/Action
rollup path is byte-identical.
- README.md, agent-consumption.md: author family's top-level skill is now
al-code-author.
R26 generalization and the al-table-author leaf from #67 are unchanged.
Knowledge article count unchanged at 199.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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>
