Decide which plugin features should ship as mods #5778

Activity

1. github-actions

   added

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 2, 2026
2. kyle-sexton commented on Oct 4, 2026

   

   kyle-sexton

   on Oct 4, 2026

   ContributorAuthor

   More actions

   This was generated by AI during triage.

   Routing: human-gated, status: needs-decision, work class structural (C4). This is a product and architecture decision (which plugin features move to a new runtime surface, how the marketplace versions and tests it, and whether the skills-versus-hooks split in the plugin philosophy changes), and any adoption supersedes ADR 0035's Defer.
   Basis: docs/adr/0035-defer-claude-code-mods-with-five-go-criteria.md (Defer; no plugin gains a modules key until all five go criteria hold); docs/upstream/claude-code-mods/go-no-go.md ("After a run": a flip to go needs a superseding record and reopens the guard-conversion conditions rather than lifting them).

   Sequencing, by the issue's own text: start after the context-guard pilot (#5777) reports. Upstream blocker today: go criterion 3 fails (anthropics/claude-code#92533 is OPEN, checked 2026-10-04), so no answer here can ship yet. #5768 re-runs the go/no-go runbook. No blocked-by edges were added; the chain is reported to the maintainer.

   Already in the repository, for when this is picked up: the mod-authoring convention (how a marketplace plugin would ship a mod: version floor, mod versus settings hook) answers part of question 2, and ADR 0035's Consequences answer part of question 1 (the hook budget is max-shaped, so lower process fan-out moves the budgeted wall only if the guardrails dispatcher is replaced; mods cannot take per-repository configuration).

   Agent Brief

   Type: Task
   Summary: Decide which plugin features, if any, should ship as mods, and how the marketplace versions and tests mods.

   Current behavior:
   Mods are deferred. Plugin behavior ships as skills and settings hooks only.

   Desired behavior:
   A recorded decision (an ADR superseding or amending ADR 0035) that answers the issue's three questions, each with evidence: which plugins' hook behavior a mod would do better and why; the versioning and test cadence for an early-access API; and whether the skills-versus-hooks split in the plugin philosophy changes.

   Acceptance criteria:

   • Each of the three questions has an answer with its basis.
   • The answer to question 1 names, per candidate plugin, the benefit claimed and the evidence for it, including the Pilot a mod producer for context-guard and rate-limit-guard #5777 pilot result.

   Out of scope:

   • Implementing any mod.
   • Re-running the go/no-go runbook (docs: re-run the mods go/no-go after Claude Code 2.1.287 shipped mods #5768).
3. kyle-sexton

   added

   priority: lowNice-to-have, cosmetic, or speculative; opportunistic.Nice-to-have, cosmetic, or speculative; opportunistic.

   needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

   status: needs-decisionAwaiting a human or maintainer judgment call.Awaiting a human or maintainer judgment call.

   work-class: structuralRefactors, migrations, contract changes; cross-cutting and hard to reverse.Refactors, migrations, contract changes; cross-cutting and hard to reverse.

   and removed

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 4, 2026
4. kyle-sexton

   closed this as completedin #6152on Oct 4, 2026