David Alonso's personal Claude Code plugins, served as a marketplace.
/plugin marketplace add DvAlonso/claude-plugins
Draft structured handover documents that brief a fresh agent or human teammate on a focused task with enough context to start cold — instead of relying on context compaction, which silently drops detail.
/plugin install handover@dalonso
Invoke with /i-handover (or just ask for "a handover"). The skill walks a
9-section anatomy (mission, audience, scope boundaries, where to start,
method, tools, output format, disposition, suspicions), holds the draft to a
quality bar, and saves it to docs/handovers/YYYY-MM-DD-<topic>.md. A
project can carry its own customized workflow doc at
docs/workflows/handover.md — when present, it wins over the bundled one.
Terse Done / Check / You / Next end-of-turn format, enforced. Each section is a bulleted list of short items, never prose paragraphs. A SessionStart hook injects the contract (what each section carries, when sections are omitted, the one-time "expand" escape for a detailed Done); a Stop hook checks turns that did real work — edits, commands, MCP writes — and re-prompts when the final message lacks a Done section. Conversational and read-only turns stay plain prose.
/plugin install turn-format@dalonso
The switch: enable/disable the plugin (globally via /plugin, per project
with "turn-format@dalonso": false in .claude/settings.local.json). Plugin
config offers mode (block default / nudge / off) and
inject_context. After two consecutive re-prompts in a turn the hook stands
down rather than loop.
Write and maintain a project's orientation articles — the five that let a project manager, a teammate, or a fresh agent open a staging environment with no context and answer two questions: is this ours to do at all, and is what I am looking at a fault, a gap, or a deliberate choice. Four are filled in from what the project already contains (specification, tracker, code, conventions). The fifth — what was agreed with the client and what was explicitly excluded — is created as an empty skeleton, because it is commercial fact that lives with whoever scoped the work, and an invented exclusion is worse than a blank one.
/plugin install project-intro@dalonso
Invoke with /project-intro (or ask to "write the project intro" / "update
where we are at"). It writes to the zeypm knowledge base when that MCP is
available and falls back to docs/orientation/ when it is not. Two modes,
chosen by what it finds: scaffold when no orientation set exists, refresh when
one does — and refresh rewrites only the status article, since the other three
are stable by design. Articles are left as drafts; publishing asserts they are
correct, which is a person's call. Its governing rule is that it never invents:
where the project cannot tell it something, the article says so.
Unlike a build-artifact marketplace, this repo is the canonical source —
edit here, bump the plugin's version in its plugin.json, push, and
installed clients pick the update up on their next marketplace refresh.
MIT licensed.