bee:pre-dev-research

Dispatch parallel agents to analyze codebase patterns and write research.md findings.

2|1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/luanrodrigues/ia-frmwrk --skill bee-pre-dev-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bee:pre-dev-research
Source: https://github.com/luanrodrigues/ia-frmwrk/tree/main/pm-team/skills/pre-dev-research
Command: npx skills add https://github.com/luanrodrigues/ia-frmwrk --skill bee-pre-dev-research

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the crucial pre-development research phase, ensuring that new features and modifications are built on a solid foundation of existing codebase patterns, industry best practices, and user needs, thereby preventing costly rework and misaligned development.

Core Features & Use Cases

  • Parallel Research Dispatch: Simultaneously gathers insights from codebase analysis, external best practices, framework documentation, and user/UX research.
  • Context-Aware Research Modes: Adapts its approach based on whether the task is greenfield development, modification of existing code, or integration with external systems.
  • Structured Output: Consolidates all findings into a research.md file, complete with file:line references, URLs, and synthesized actionable insights.
  • Use Case: Before starting a new API feature, this skill will analyze the existing API codebase for patterns, research external best practices for similar APIs, check the relevant framework documentation for constraints, and validate the user problem, all before any PRD is written.

Quick Start

Initiate pre-development research for a new feature by running the pre-dev research skill.

Frequently Asked Questions about bee:pre-dev-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I conduct pre-development research for a new software feature?

Pre-development research analyzes codebase patterns, external best practices, framework documentation, and UX research in parallel. It outputs findings to a research.md file with file:line references and topology configuration before any PRD is written.

What is the best way to analyze an existing codebase before modifying it?

Analyzing an existing codebase before modification involves dispatching parallel agents to review current patterns and framework constraints. This context-aware research mode ensures new code aligns with established architecture and industry standards.

How do I gather framework documentation and UX research before writing code?

Gathering framework documentation and UX research before coding is done by dispatching parallel agents to collect external best practices and validate user needs. This ensures new features are built on a solid foundation of industry standards.

Can I use pre-development research for greenfield, modification, and integration scenarios?

Yes, pre-development research supports greenfield, modification, and integration scenarios. It adapts its analysis approach based on the specific development context to prevent costly rework and misaligned development.

Does pre-development research output structured file references for codebase analysis?

Yes, pre-development research outputs structured findings to a research.md file complete with file:line references, URLs, and synthesized actionable insights. This consolidates all research into a single accessible document.