docs: surface composition in user-facing docs#257
Merged
mlieberman85 merged 1 commit intoMay 13, 2026
Conversation
Post-013 doc catchup. The 013-plugin-composition feature shipped in kusari-oss#251-kusari-oss#256 but only docs/IMPLEMENTATION_GUIDE.md (the dev-facing implementation reference) mentioned it. End-users coming through README / getting-started / packaging-plugins had no path to discover composition. Four small edits, all cross-link to the existing specs/013-plugin-composition/ quickstart and spec — no new user-facing doc page created (option A from the scope question; the quickstart already serves as the canonical walkthrough): - README.md: added "Composition" to the Features bullet list; added a paragraph in "Creating a Plugin" pointing composite authors at the quickstart instead of the full plugin-packaging flow. - docs/getting-started/README.md: added a fourth "Choose Your Path" section for org-specific posture composition, with links to the quickstart, TOML schema contract, and the Implementation Guide's composition section. - docs/getting-started/implementation-development.md: added the composition quickstart to "Next Steps". - docs/packaging-plugins.md: added a "Composition vs forking" section above "See also" with four canonical links (quickstart, spec, TOML schema contract, Implementation Guide §12) and a one-sentence rule of thumb on when to compose vs fork. All links resolve. Full test suite: 2108 passed / 6 skipped / 0 failed (unchanged from post-013 baseline; this is docs-only). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Post-013 doc catchup. Feature 013-plugin-composition shipped via #251–#256, but only
docs/IMPLEMENTATION_GUIDE.md(the dev-facing implementation reference) mentioned it. Users coming through README, the getting-started flow, or the third-party plugin packaging guide had no path to discover composition.Four small surgical edits cross-link to the existing
specs/013-plugin-composition/quickstart.md— no new user-facing doc page is created. The quickstart already serves as the canonical walkthrough.Test plan
specs/013-plugin-composition/{quickstart,spec}.md,specs/013-plugin-composition/contracts/toml-schema.md,docs/IMPLEMENTATION_GUIDE.md#12-...)## 12. Composition (assembling implementations from other implementations)headingChanges
README.mddocs/getting-started/README.mddocs/getting-started/implementation-development.mddocs/packaging-plugins.md🤖 Generated with Claude Code