bee:using-pm-team

A research-first pre-development workflow is a mandatory planning phase that clarifies requirements, architecture, and tasks before coding begins, using specialized agents to research codebase patterns and best practices to prevent costly rework and scope creep.

To plan a complex software feature, you run a Large Track workflow with 10 gates that guides you through research, PRD creation, TRD, API design, data modeling, and task breakdown to ensure thorough preparation before development starts.

Yes, you can use the Small Track workflow designed for simpler features, which scales down the planning process to 5 gates, ensuring appropriate planning depth without unnecessary overhead for tasks taking less than two days.

Systematic feature development generates detailed planning artifacts including Product Requirements Documents, Technical Requirements Documents, API designs, data models, and atomic task breakdowns to define the implementation roadmap.

Yes, the workflow includes a delivery tracking skill that monitors execution progress against the planned roadmap, ensuring that the implementation phase follows the structured tasks defined during the pre-development gates.

You should avoid a structured pre-development planning phase for trivial changes or hotfixes that require immediate deployment, as the mandatory research and documentation gates would introduce unnecessary delay to urgent agile workflow corrections.