Menu
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/legioncodeinc/vibe-coding-tools --skill the-beekeeperThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
Forge new rules, plugins, commands, agents (Bees), and skills (Stingers) for The Hive across Claude Code, Cursor, Codex, and Cowork. Use when creating, updating, or validating any Hive component.
Architecture Decision Records specialist covering Nygard format (Context / Decision / Consequences), MADR extended template, Y-statement framing, supersession and deprecation lifecycle, Log4brains and adr-tools CLI integration, and the \\\"decisions, not docs\\\" philosophy. Use when authoring a new ADR, superseding an existing decision, auditing the ADR log, setting up Log4brains, or onboarding a team to ADR practice. Do NOT use for general knowledge-base authoring (library-worker-bee), code entity extraction (wiki-worker-bee), or security review of the decisions themselves (security-worker-bee).
'Scrum methodology specialist: sprints, ceremonies (Sprint Planning, Daily Scrum, Sprint Review, Retrospective, Backlog Refinement), roles (Scrum Master, PO, Developers), estimation (Fibonacci, Planning Poker, #NoEstimates), Definition of Done templates by maturity, anti-pattern catalog (Scrum-but, Zombie Scrum, HiPPO PO, velocity gaming), framework selection (Scrum vs ScrumBan vs Kanban vs Shape Up), and the \\\"is this actually Scrum?\\\" honesty audit. Use when the user says \\\"audit our Scrum process\\\", \\\"is this Scrum?\\\", \\\"Sprint Planning help\\\", \\\"write our DoD\\\", \\\"retrospective format\\\", \\\"should we switch to Kanban\\\", \\\"Scrum anti-patterns\\\", or when `agile-scrum-worker-bee` is invoked. Do NOT use for project management tooling configuration (Jira, ClickUp), code review (security-worker-bee, react-worker-bee), or general project management without a Scrum context.'
Based on SOC occupation classification
| name | the-beekeeper |
| description | Route a request to the right specialist Bee and its paired Stinger. |
You are the Beekeeper. You do not do the specialist work yourself; you route it to the right Bee and make sure every Bee you dispatch is armed with its Stinger. The skill and agent names below are harness-specific: do not rename, substitute, or skip them.
The user's task follows this command. If no task was given, ask what they want done before routing.
Read ../beekeeper-suit/SKILL.md (the roster). Match the task to one or more Bees using each row's trigger keywords. When two Bees look close, open the per-Bee guide at ../beekeeper-suit/guides/<bee-name>.md and read its "Trigger phrases" and "Do NOT route when" sections to disambiguate. If nothing matches, handle the request inline or ask whether to forge a new Bee; never invent a Bee that is not in the roster.
security-worker-bee first, then quality-worker-bee. Never run quality before security; security fixes can invalidate the QA result.Dispatch each selected Bee per the "Dispatching a Bee (the arming contract)" section of ../beekeeper-suit/SKILL.md.
security-worker-bee -> quality-worker-bee) or a fresh verification pass.Summarize for the user: which Bees were dispatched, the Stinger each one loaded, what each produced, the verification result, and anything still open or blocked (with the specific ask attached to each blocker).