Skip to content

feat: ship role protocols as per-role plugin skills - #69

Draft
notdp wants to merge 5 commits into
mainfrom
role-skills
Draft

feat: ship role protocols as per-role plugin skills#69
notdp wants to merge 5 commits into
mainfrom
role-skills

Conversation

@notdp

@notdp notdp commented Jul 14, 2026

Copy link
Copy Markdown
Owner

Role protocol text — the nine duo/squad role specs — now ships as per-role plugin skills (hive:duo-worker, hive:core, …) over the marketplace auto-update chain, so spec iteration reaches live Claude and Codex panes without cutting a CLI release. Previously every prose tweak rode on a version bump plus pipx upgrade.

Design decisions worth reviewing:

  • Each role is its own skill instead of reference files inside the umbrella hive skill. Spawned panes get their role skill activated by name as line one of the launch turn, so the birth prompt shrinks to identity + idle discipline and the model never constructs a spec path itself.
  • Dispatched running panes are told to invoke the skill by name; resumed sessions keep skill=none — their protocol already lives in the session history.
  • The hive skills command group and src/hive/core_assets/specs/ are removed outright: single-user cutover, no compatibility shim.

Validation: accepted by a codex validator after three review rounds, including a real-install loop — codex plugin add materializes the per-role skills under the plugin cache, and a source-spawned pane loads its role skill by name from that install.


Compound Engineering
Claude Code

notdp added 5 commits July 14, 2026 15:28
…group

Role protocol text now lives in plugins/hive/skills/hive/references/ and
reaches both Claude and Codex panes through the marketplace auto-update
chain, so spec iteration no longer rides on a CLI release. The skills
command group and core_assets/specs are removed outright (single-user
cutover, no compatibility path); birth prompts, adoption hints, and init
`next` fields route through the hive skill's references instead.
Each role ships as its own plugin skill (hive:duo-worker, hive:core, ...)
instead of reference files inside one skill. Spawned panes get the role
skill activated as line one of the launch turn (Agent.spawn skill kwarg),
so the birth prompt shrinks to identity + idle discipline and no path is
ever constructed by the model; dispatched running panes are told to
invoke the skill by name. Resumed sessions keep skill=none — their
protocol already lives in the session.
@notdp notdp changed the title wip: role-skills feat: ship role protocols as per-role plugin skills Jul 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant