Add RFC-0009: Extended Skill Bundles#27
Draft
jwm4 wants to merge 1 commit into
Draft
Conversation
Companion to RFC-0008 (MVP Skill Registry). Extends bundle membership to register non-skill content with a generic, free-form member_type field and adds trace integration for non-skill members. This is an intentionally lightweight draft covering introduction, motivation, and user journeys only. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
jwm4
marked this pull request as draft
July 23, 2026 20:47
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
member_typefieldScope
This draft is intentionally limited to introduction, motivation, and user journeys. It contains no technical implementation details (no schema, store interface, API endpoints, SDK signatures, or CLI mapping). The goal is to get alignment on the approach before filling in specifics.
If reviewers would like more detail on any aspect, I am happy to add it. Alternatively, implementation details can be left to the implementer since the user journeys and motivation should be sufficient to define the scope.
Test plan
member_typeapproach covers known harness component typesPosted by Bill Murdock with assistance from Claude Code.