pre-dev-research

To gather codebase patterns and best practices before writing a PRD, dispatch parallel research agents to scan repo patterns, external practices, and framework docs, producing a validated research.md with file:line references and version constraints.

Pre-development research is the process of analyzing existing codebase implementations, external best practices, and framework documentation to inform TRD creation, ensuring technical requirements align with current architecture and SDK constraints.

Research existing implementations and tech stack constraints by running three parallel agents that return file:line references, external URLs, and version constraints, aggregating their outputs into a structured research document for feature planning.

Yes, you can use parallel agents to research framework documentation for a Stripe integration by dispatching them to collect external URLs, SDK constraints, and recommended architectures, which are then synthesized into a comprehensive research.md file.

The best way to prevent misaligned implementations during feature planning is to enforce a Gate 0 blocking checklist that validates research mode, ensuring all agents return required artifacts like file references and tech versions before PRD creation begins.

Yes, pre-dev research requires declaring a research mode during Gate 0 validation to ensure the parallel agents properly execute and return the necessary file:line references, external URLs, and version constraints for the research.md output.