claude

vdm-comms

Meetings and correspondence discipline for repositories that keep them as files: a configurable contract linter for meetings/<date>-<slug>/ and series files (the contract is a floor distilled from three repositories — a track may resolve as a directory or a single file, index.md is owed only after the meeting has happened), with a project's own conventions switched on by name (comms.meeting-rules); meeting files split by who reads them — the agenda the owner's, the pitch what the counterpart hears, matched by topic name, with plugin templates for agenda, prep, pitch and index; a drift signal for the generated registry and per-track meeting pointers, written as markdown or Obsidian wikilinks with participant, topic and material columns; a PreToolUse guard that refuses to mark an outgoing letter sent — by creating it so or by an edit — without `sent-proof:` — the sending tool's id or that of what the owner sent by hand, checked with the access layer where it is installed, down to who the send went to, or the owner's word — and a PostToolUse check that names one a shell command left so, and a linted attachment checklist the sender can click; the form of an outgoing draft checked per its declared `channel:` (a subject line for email, a separator before the text to send — configurable per project, drafts only), and a draft declared outside comms/ named; each paragraph of a draft's text on one line, on every channel whose receiver keeps line breaks (all but comms.markdown-channels, intercom by default); a PreToolUse guard that keeps the raw .eml out of comms/ and the meetings tree, on Write and on a copy in Bash; who may write to a person and how to address them — `trust`, `addressed_as` and the From pairs in the HQ's people/, which a project without its own finds by asking the access layer for its HQ; and a pending-item summary — who owes what by when, series queues, unsent drafts, meetings without a transcript. The wording of everything it writes into the project is con

0 on GitHubby Dmitry Vorobyevv0.42.1MITupdated 3 days agoworkflow
/

Plugin vdm-comms from marketplace vodmal in VoDmAl/ai-dev-plugins. Commands read from the repo's manifest — 2 days ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (4)

  • index

    Rebuild the generated layer over a meetings tree: the INDEX.md registry, the per-series meeting lists, and the pointer each track's comms/ gets for a meeting that touched it. Use when the session-start signal says artefacts are behind, after adding or editing a meeting, or when a track's chronology

  • letters

    The communications skill: what an outgoing text — a letter, a chat message, an SMS, a ticket comment — carries and what stays out of it: goal, one subject, the addressee, register, claims with a source, the sender's commitments, who may write to a person (`trust` in the HQ's people/), the cutting pa

  • meetings

    Meetings and correspondence discipline for a repository that keeps them as files — meetings/<date>-<slug>/ with agenda/prep/index, per-series files, and comms/ letters on tracks. Use when writing or fixing a meeting file, when the contract linter reports a violation, when onboarding a repo that alre

  • pending

    Who owes what, to whom, and by when — a summary of open items across the files a project declares, grouped by owner, with overdue and due-this-week separated out. Use when the session starts with «что висит», before preparing a recurring meeting, when closing a session, or when an item needs an owne

Hooks (9)

  • SessionStart

    "${CLAUDE_PLUGIN_ROOT}/scripts/comms-index-check.sh"

  • SessionStart

    "${CLAUDE_PLUGIN_ROOT}/scripts/comms-pending-check.sh"

  • PreToolUse

    "${CLAUDE_PLUGIN_ROOT}/scripts/comms-draft-guard.sh"

  • PreToolUse

    "${CLAUDE_PLUGIN_ROOT}/scripts/comms-eml-guard.sh"

  • PreToolUse

    "${CLAUDE_PLUGIN_ROOT}/scripts/comms-versions.sh"

  • PostToolUse

    "${CLAUDE_PLUGIN_ROOT}/scripts/comms-lint.sh" --hook

  • PostToolUse

    "${CLAUDE_PLUGIN_ROOT}/scripts/comms-pending.sh" --hook

  • PostToolUse

    "${CLAUDE_PLUGIN_ROOT}/scripts/comms-versions.sh"

  • PostToolUse

    "${CLAUDE_PLUGIN_ROOT}/scripts/comms-sent-check.sh"

View source on GitHub

More from VoDmAl/ai-dev-plugins

All 4 plugins →

vdm

claude

SDLC workflow plugins: docs-sync (documentation synchronization), docs-distill (synthesis layer — the summary view nobody rebuilds because nobody asks; discovery + drift signal via `covers:` frontmatter, crystal harvest on cut, two-way handoff with docs-sync), learn (knowledge capture), changelog (project change tracking), crystal-* (multi-root workitem discipline gate — grow/bud/cut/cave/migrate with auto-scan + 4-tier status taxonomy + in-flight capture-reminder + orphan-sidetracks gate + batch legacy-doc migration + evidence discipline: Basis taxonomy, pre-action gate, live current-model section), intercom (central cross-agent/cross-session message store outside all repos, git-remote-identity routing + agent directory: auto-aliases + user-said names + description, SessionStart identity check, hard-stop on unresolved targets), wrap (pre-clean-session check: chat-only items written to their homes, one commit, a start phrase with a slug), retro (do the shared rules work: the owner's turns across every session on the machine, read against the rules each session received), and a lesson folded into the shared rules by a subagent rather than appended — the layer may be rewritten, a change to what sessions receive is shown to the owner first, and a writer installs it only over the version it was made from, with a history of the last 50.

12 skills · hooks

0

vdx

claude

Unified lifecycle interface (up/down/build/test/check/fix/publish) + versioned maturity audit + AI bootstrap skill + how the agent is launched (vdx ai: session-start check, skill). MCP server: the installed vdx-mcp, else npx from @vodmal/vdx-cli on npm.

2 skills · 1 MCP server · hooks

0

vdm-git

claude

Git safety plugin: blocks commit/push until user confirms, ships `git-guard-prepare` helper for file-based commit hand-off, enforces commit message format, crystal-completion backup gate, U+FFFD corruption guard on both commit surfaces.

1 skill · hooks

0

Similar plugins

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

backend-development

claudecodex

Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development

9 skills · 1 command · 8 agents

wshobson/agents 42,461

beads

claudecodex

AI-supervised issue tracker for coding workflows

1 skill · 1 agent · hooks

gastownhall/beads 28,698

minimax-skills

claude

MiniMax AI skills library for frontend, fullstack, Android, iOS, shader, GIF sticker, document, presentation, spreadsheet, and multimodal media workflows

18 skills

MiniMax-AI/skills 13,828

worktrunk

claudecodex

Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows. This plugin provides configuration guidance (LLM commit messages, project hooks, worktree paths), automatic activity tracking (🤖/💬 indicators in `wt list` showing active Claude sessions), and a `/wt-diff` pane showing each worktree's changes.

2 skills · hooks

max-sixty/worktrunk 12,481

gsd-core

claude

GSD Core is a meta-prompting, context engineering, and spec-driven development system for AI coding agents.

72 skills · 72 commands · 64 agents · hooks

open-gsd/gsd-core 11,494

Maintain vdm-comms?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins4 plugins