Skip to content

docs: replace restated upstream facts with pointers in dometrain, event-storming, instruction-placement, adhd #12693

Description

@kyle-sexton

Refs: #7292

Outcome

28 passages in 8 files state a fact an external source owns. Rewrite each as a pointer to the live upstream section, or remove it, so the next upstream change cannot leave a stale copy here. Plugins: dometrain, event-storming, instruction-placement, adhd.

Done when

  • Every row below is fixed: the restated value is deleted, the local decision stays in this repository's own words, and the pointer goes to the exact upstream section with an as-of date and a recheck trigger, per .claude/rules/skill-bodies-state-current-rules.md. A record beside a restated value does not fix it. A row marked Remove has no local dependency on the fact.
  • The PR passes check-stamps.sh --trigger-less (plugins/attribution/skills/audit/scripts/check-stamps.sh) on the files it touches.
  • Each touched plugin has a changelog fragment.

Rows

dometrain

  • plugins/dometrain/README.md:3-7 (r154). Pointer: https://github.com/Dometrain/mcp#1-get-an-api-key (confirm the section) Drop the server URL, closed-source claim and subscription requirement; keep that this plugin ships no MCP server and its skills call one, and point at Dometrain's setup section.
  • plugins/dometrain/README.md:18-20 (r155). Pointer: https://github.com/Dometrain/mcp#2-install Drop the claim of which variable Dometrain's plugin reads; keep this plugin's decision to register a user-scope server named dometrain and read the key from an environment variable, and point at the section.
  • plugins/dometrain/README.md:62-75 (r156). Pointer: https://github.com/Dometrain/mcp#claude-code Delete the restated install commands, license note and CLI flag-support caveat; keep that Dometrain ships its own plugin as an alternative, and point at its Claude Code install section.
  • plugins/dometrain/README.md:83-84 (r157). Pointer: https://github.com/Dometrain/mcp#2-install Drop the description of how Dometrain's plugin bundles the server and authenticates; keep that this plugin ships skills only and uses the user-scope server, and point at the section.
  • plugins/dometrain/README.md:86-91 (r158). Pointer: https://code.claude.com/docs/en/plugins/manifest-reference#name (confirm the section) Drop the claims about install identity, namespacing and undocumented same-name behavior; keep the rule not to enable both dometrain plugins, and point at the manifest name section.
  • plugins/dometrain/skills/setup/SKILL.md:42-45 (r148). Pointer: https://github.com/Dometrain/mcp#troubleshooting Drop the statement of which rejection codes stop the tool from resolving; keep the decision to report connected on resolution and claim nothing about API access, and point at Troubleshooting.
  • plugins/dometrain/skills/setup/SKILL.md:58-62 (r150). Pointer: https://code.claude.com/docs/en/mcp#environment-variable-expansion-in-mcpjson Drop the claim that Claude Code expands the variable from its own environment at connect time; keep the instruction to start a new session after setting the variable, and point at the section. Same text also at: plugins/dometrain/README.md:28-29; a row of its own covers it only if listed.
  • plugins/dometrain/skills/setup/SKILL.md:110-115 (r151). Pointer: https://code.claude.com/docs/en/plugins/manifest-reference#defaultenabled Drop the description of what defaultEnabled false does to installs and skill availability; keep the rule that the enable step is required with an explicit scope flag, and point at the section. Same text also at: plugins/dometrain/README.md:53-54; a row of its own covers it only if listed.
  • plugins/dometrain/skills/setup/SKILL.md:124-128 (r153). Pointer: https://github.com/Dometrain/mcp (confirm the section) Drop the statement of Dometrain's plugin.json name; keep the decision not to detect collisions by MCP tool-name prefix, and point at the Dometrain repository's manifest. Same text also at: plugins/dometrain/README.md:62-64; a row of its own covers it only if listed.

event-storming

instruction-placement

adhd

  • plugins/adhd/README.md:92-97 (r007). Pointer: https://code.claude.com/docs/en/hooks#sessionstart Drop the statement that a SessionStart or UserPromptSubmit hook injects context; keep the decision to build an opt-in hook only on demonstrated demand, and point at the section.

Notes

Lines are as of 3bd42cabfe (https://github.com/melodic-software/claude-code-plugins/blob/3bd42cabfe6bdef37a05778d396869af0381bb51); locate each passage by its text if main has moved. Each rNNN is that row's number in the order of #7292's "Findings by plugin". Every row was upheld by three blind judges and survived a refutation pass, run report-only for #12072. Pointers are candidates: fetch each before writing it, and confirm the section still documents the fact.

Parent: #7292

Activity

  1. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 3, 2026
  2. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor

    The triage sweep dispatched intake triage for this issue (attempt 1 of 2).

  3. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor

    Proposed work class: work-class: scoped
    Basis: automated intake triage; the lanes App applied this class.

    Size: Medium
    Complexity: Low
    Uncertainty: Knowable
    Flags: none
    Blocked by: none

    Understood: a docs-only cleanup. 28 passages across four plugins (dometrain, event-storming, instruction-placement, adhd) restate facts that upstream sources own. Each should become a local decision plus a dated pointer to the upstream section, with a changelog fragment per plugin and a clean check-stamps.sh --trigger-less run. The rows, pointers and done-when are specific. Several pointers are marked "confirm the section", so each one needs checking against the live upstream page before it is written. No duplicates found among open issues; this is a child of #7292.

    Automated triage, applied by the lanes App.

  4. added
    priority: lowNice-to-have, cosmetic, or speculative; opportunistic.
    and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 3, 2026
  5. added
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.
    on Nov 3, 2026
  6. added
    admission-deferredAdmitted but waiting for WIP room; the hourly work-unblock sweep labels it agent-ready.
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    and removed
    admission-deferredAdmitted but waiting for WIP room; the hourly work-unblock sweep labels it agent-ready.
    on Nov 3, 2026
  7. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor
    No description provided.
  8. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor
    No description provided.
  9. melodic-automation-lanes commented on Nov 3, 2026

    @melodic-automation-lanes
    Contributor

    This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41591208749, the work-resolve-issue run that agent-ready started, before it did any work; that run ended at 2026-11-03T08:45:17Z. work-unblock has now removed and added agent-ready back to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last added agent-ready or a run last reported, work-unblock waits longer before each one, up to 24 hours.

  10. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    and removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 3, 2026
  11. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor
    No description provided.
  12. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor
    No description provided.
  13. removed
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: lowNice-to-have, cosmetic, or speculative; opportunistic.work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.

    Type

    Fields

    Work status

    agent-ready

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions