Product
The Hive that builds and ships software.
Developer, QA Engineer, Product Manager, Technical Reviewer, Security Analyst. The full loop from spec to merged PR.
The Product Hive is the most code-aware of the starter teams. It's built to take a feature idea from "draft a spec" through "open a pull request" and stop at every approval gate in between. If your work touches a repo, this is your Hive.
The roster
| Role | What they do |
|---|---|
| Product Manager | Drafts specs, writes user stories, breaks features into tasks, keeps the why front and center. |
| Developer | Reads the spec, writes the code, opens the PR. Handles refactors, bug fixes, scaffolding. |
| QA Engineer | Reviews implementation against acceptance criteria, writes tests, runs them, flags regressions. |
| Technical Reviewer | Reads code for clarity, maintainability, and consistency with the rest of the codebase. |
| Security Analyst | Catches credential leaks, unsafe input handling, missing auth checks, dependency risks. |
Five roles, but you rarely use all of them on a single task. Queen Bee routes to whichever subset the work needs.
What the Hive handles well
- Feature builds - spec → implementation → PR → review.
- Bug fixes - reproduce, diagnose, patch, test.
- Refactors - proposal, staged migration, regression checks.
- Code reviews - drop a PR URL, get a structured review back.
- Spec writing - sketch an idea, get a working spec with acceptance criteria.
It's less suited for green-field design work (use Marketing or a custom Hive with a Designer in it) or non-code operational work (Operations).
Setup checklist
Get the most out of the Product Hive by:
- Linking a GitHub repo to the project. Without it, agents can't open PRs.
- Setting
qualityTier: standardorpremiumon tasks that require careful reasoning (architecture, security review). Budget tier is fine for routine work. - Adding env vars for any services the agents need to test against (API keys, test database URLs).
- Connecting Slack if you want PR-ready notifications in a channel.
Example tasks
- "Implement the password-reset endpoint described in [Notion page]. Open a PR against
main." - "Review PR #412 - focus on the new RLS policies."
- "There's a flaky test in
src/tests/auth.test.ts. Diagnose and fix." - "Draft a spec for adding SSO to our login flow. Include acceptance criteria and migration notes."
What's next
Most product work pairs nicely with marketing follow-up. Once your Product Hive ships a feature, hand the announcement to the Marketing Hive.