Plugin Claude Code
Beevibe Claude Code plugins for sharing, researching, and coordinating AI agent work.
Plugin Claude Code
Beevibe Claude Code plugins for sharing, researching, and coordinating AI agent work.
Skill Claude CodeCodex
Find the best GitHub repo for a goal, then call userepo to run it in a sandbox. Use whenever the user's goal requires a capability you don't have natively and you haven't been given a specific repo.
Skill Claude CodeCodex needs its repo
Cold-start git workspace setup for a fresh beevibe task. Use at the start of a session whose intent has a block but NO or block — i.e. the first dispatch of this task. Checks for an existing repo clone, pulls the base branch if present (clone if missing), prunes any per-task worktrees from earlier tasks whose work has…
Skill Claude CodeCodex
Multi-round negotiation protocol — covers both initiator and peer roles. Use when about to call negotiate(), when receiving a intent block as a peer, or when receiving an 'escalated' sentinel from a blocked respondnegotiate. Covers proposal crafting, counter-strategy, deadlock detection, when to accept early…
Skill Claude CodeCodex needs its repo
You are the child agent inside a fresh Docker sandbox. Borrow the given GitHub repo, produce a real artifact for the goal, and export it. Do not review the repo. The proof is that it works.
Skill Claude CodeCodex
CI verification before marking a PR-bearing task done. Use BEFORE calling mcpbeevibeupdateprogress(done) on any session whose deliverable is a pull request — including the first dispatch (you opened the PR with gh pr create) and any revision dispatch (you pushed new commits to an existing PR). Watches the PR's…
Plugin Claude Code
Beevibe Claude Code plugins. Currently: Architecture Deep Research (live, evidence-only research for system-design decisions).
MCP server Claude CodeCodexCursor +2
MCP server "adr" as configured in beevibe-ai/beevibe-cto. Launched with adr-mcp. Needs 8 environment variables to run.
Skill Claude Code
Architecture Deep Research — scan the current repo, draft a PRD, and run the deep-research loop with citation audits. Use when the user asks you to make an architecture decision, asks "what topology should we use?", says they need to pick between options like vector stores / message queues / retrieval patterns /…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: