research-orchestrator

You can gather ticket context automatically by using a research orchestrator that dispatches parallel subagents to investigate GitHub issues or Notion pages. It loads source-specific strategies to collect git history, related codebase files, and linked issues into a comprehensive report.

Parallel research orchestration for codebase analysis is the process of dispatching multiple subagents concurrently to investigate different aspects of a ticket. This mechanism ensures all necessary information, such as commit history and related code, is collected before development begins.

Yes, the ticket context research orchestrator works with both Notion and GitHub sources. It adapts its research methods by loading source-specific strategies to leverage platform-specific data, ensuring comprehensive context gathering regardless of the ticket origin.

You optionally need the gh CLI and Notion MCP to run ticket research orchestration, as they provide platform-specific data access. However, the only strict requirement is that ticket-intake completion must be finalized before the research orchestration can begin.

To compile a research report for a new feature request, the orchestrator analyzes the GitHub issue description, linked issues, commit history, and relevant code files concurrently. It then aggregates these parallel findings into a detailed report for developers.