famdeck-relay

Plugin famdeck-relay from marketplace ivintik in iVintik/private-claude-marketplace. Commands read from the repo's manifest — 1 month ago.

Skills (8)

• handoff

  Save current work context as a handoff for later pickup — captures branch, uncommitted changes, decisions, next steps, and active issues. Use when the session is ending, switching to a different task, or parking work. Trigger proactively when work is being paused. Do NOT use for picking up existing

• messaging

  Send cross-project messages and check inbox via Agent Mail — coordinate between agents, send notifications, and read messages. Use when an agent needs to notify another project, check for incoming messages, or acknowledge messages. Do NOT use for within-project context transfer (use handoff) or issu

• pickup

  Resume work from a handoff — list pending handoffs or restore full context from a specific one. Use when continuing from a previous session or checking what work is parked. Do NOT use for creating new handoffs (use handoff) or routing issues (use relay).

• relay

  Route issues and manage trackers across projects — create bugs, tasks, and features in GitHub, GitLab, Jira, or beads; check issue status; configure trackers. PROACTIVE — trigger when you discover bugs or needed fixes in any project, especially cross-project. Do NOT use for creating handoffs (use ha

• bmad-import

  Import BMAD story and epic artifacts into Beads as trackable issues with dependencies. Use when the user says 'import stories', 'sync BMAD into Beads', 'import epics', or when Beads has no issues but sprint-status.yaml has backlog stories. Shows a dry-run plan before applying. Can filter by specific

• issue

  Create and route an issue to the correct tracker — GitHub, GitLab, Jira, or beads — based on the project's relay config. Use when the user wants to file a bug, log a task, request a feature, or report a problem. PROACTIVE — trigger automatically when you discover a bug or needed fix in any project,

• status

  Show a unified issue dashboard across all configured trackers — GitHub, GitLab, Jira, beads. Use when the user wants to see what's open, review work across projects, or get a cross-tracker overview. Do NOT trigger for creating issues (use relay:issue), configuring trackers (use relay:trackers), or p

• trackers

  Manage per-project issue tracker configuration in .claude/relay.yaml — show, initialize, add, or remove trackers. Use when the user wants to set up relay for a project, connect GitHub, GitLab, Jira, or beads, view current tracker config, or remove a tracker. Do NOT trigger for creating issues (use r

Subagents (2)

• context-gatherer

  Gather work context and save it as a handoff — captures git branch state, uncommitted changes, active beads issues, decisions made, and next steps. Use when the user wants to save progress, switch context, delegate work to another session, or says "handoff". Do NOT use for picking up existing handof

• coordinator

  Coordinate multi-agent work via Agent Mail — session bootstrap, file reservations, messaging, and conflict resolution. Use when multiple agents need to work in parallel on the same project, when file ownership needs to be handed off between agents, or when resolving agent conflicts. Do NOT use for s

MCP servers (1)

• relay

  runs: uv --directory ${CLAUDE_PLUGIN_ROOT}/mcp-server run relay-mcp

Hooks (4)

• SessionStart

  python3 ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/register-provider.py

• SessionStart

  mkdir -p ~/.local/bin && ln -sf ${CLAUDE_PLUGIN_ROOT}/bin/relay ~/.local/bin/relay

• SessionStart

  cd ${CLAUDE_PLUGIN_ROOT} && python3 -m cli.main --format text prime

• PreCompact

  cd ${CLAUDE_PLUGIN_ROOT} && python3 -m cli.main --format text prime

Similar plugins