hive
By tctinh
Orchestrate plan-first AI development with parallel autonomous agents in isolated git worktrees. Plan multi-step tasks, enforce TDD for implementations, dispatch foragers for bugs and features, execute in batched sessions with checkpoints, verify builds/tests/lints, and run systematic code reviews before merging.
npx claudepluginhub tctinh/agent-hive --plugin hiveComponent Overview
Component Details
Agents (3)
Autonomous worker executing tasks in isolated worktrees. Writes code, runs tests, reports results via hive_worktree_commit.
Plan-first AI development orchestrator. Plans features, dispatches parallel workers in isolated worktrees, merges results, coordinates reviews. The user's primary interface for Hive workflow.
Falsification-first code reviewer. Challenges implementation against plan and specs. Runs tests before giving verdicts. Opus tier cross-checks Sonnet workers.
Skills (11)
Use when bootstrapping, updating, or reviewing AGENTS.md — teaches what makes effective agent memory, how to structure sections, signal vs noise filtering, and when to prune stale entries
Use before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when reviewing implementation changes against an approved plan or task (especially before merging or between Hive tasks) to catch missing requirements, YAGNI, dead code, and risky patterns
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when working with Docker containers — debugging container failures, writing Dockerfiles, docker-compose for integration tests, image optimization, or deploying containerized applications
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when you need parallel, read-only exploration with the agent tool (Scout fan-out)
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Use when you have a spec or requirements for a multi-step task, before touching code
MCP Servers (1)
README
Similar Plugins
essentials
24 commands, 8 agents. Loops, swarms, and teams powered by Claude Code's built-in Task System. Native task dependencies, ctrl+t progress, automatic persistence.
Uses power tools
Uses Bash, Write, or Edit tools
Help us improve
Share bugs, ideas, or general feedback.