bee-pm-team

Track delivery progress against roadmap with evidence-based analysis

Lightweight 5-gate pre-dev workflow for small features (<2 days)

Complete 10-gate pre-dev workflow for large features (≥2 days)

External research specialist for pre-dev planning. Searches web and documentation for industry best practices, open source examples, and authoritative guidance. Primary agent for greenfield features where codebase patterns don't exist.

Tech stack analysis specialist for pre-dev planning. Detects project tech stack from manifest files and fetches relevant framework/library documentation. Identifies version constraints and implementation patterns from official docs.

Product Designer agent for UX research, user validation, and design specifications. Accepts feature context and research findings. Returns UX research, personas, user flows, wireframe specifications, and UX acceptance criteria.

Codebase research specialist for pre-dev planning. Searches target repository for existing patterns, conventions, and prior solutions. Returns findings with exact file:line references for use in PRD/TRD creation.

Delivery status tracking and progress reporting. Analyzes repository against delivery roadmap to calculate actual vs planned progress, identify delays, and provide insights on velocity and risk trends.

Gate 4: API contracts document - defines component interfaces and data contracts before protocol/technology selection. Large Track only.

Gate 5: Data structures document - defines entities, relationships, and ownership before database technology selection. Large Track only.

Gate 9 (Full Track) / Gate 4 (Small Track): Delivery roadmap and timeline planning. Transforms tasks into realistic delivery schedule with critical path analysis, resource allocation, and delivery breakdown. MANDATORY gate for both workflows.

Gate 6: Technology choices document - explicit, versioned, validated technology selections with justifications. Large Track only. HARD BLOCK: Must load Bee Standards and PROJECT_RULES.md before proceeding.

Gate 1.5/2.5: Design Validation - verifies UX specifications are complete before proceeding to technical architecture. Checklist-based validation that prevents incomplete designs from reaching implementation.

Gate 2: Feature relationship map - visualizes feature landscape, groupings, and interactions at business level before technical architecture.

Gate 1: Business requirements document - defines WHAT/WHY before HOW. Creates PRD with problem definition, user stories, success metrics.

Gate 0 research phase for pre-dev workflow. Dispatches 4 parallel research agents to gather codebase patterns, external best practices, framework documentation, and UX/product research BEFORE creating PRD/TRD. Outputs research.md with file:line references and user research findings.

Gate 8: Zero-context implementation steps - 2-5 minute atomic subtasks with complete code, exact commands, TDD pattern. Large Track only.

Gate 7: Implementation tasks - value-driven decomposition into working increments that deliver measurable user value.

Gate 3: Technical architecture document - defines HOW/WHERE with technology-agnostic patterns before concrete implementation choices.

12 pre-dev workflow skills + 4 research agents organized into Small Track (4 gates, <2 days) and Large Track (9 gates, 2+ days) for systematic feature planning with research-first approach.

2 hooks across 1 event