master-planner-researcher-prp

To create a research-backed plan for complex feature development, you need a Product Requirement Prompt (PRP) that integrates web research, official documentation analysis, and structured reasoning. This approach ensures execution-ready plans with atomic tasks, validation checks, and rollback procedures for one-pass success.

Task decomposition for system architecture planning breaks down complex requests into small, verifiable atomic tasks with clear dependencies. Using structured reasoning ensures each component includes validation steps and rollback procedures, reducing uncertainty in high-complexity integrations and new feature development.

You validate implementation steps for high-uncertainty projects by generating a structured PRP that includes dense context, atomic tasks with specific validation checks, and clear output contracts. Researching official documentation and best practices beforehand ensures all requirements are verifiable during execution.

Yes, you can generate execution-ready plans by synthesizing information from web searches and official documentation analysis. Integrating these sources with structured reasoning creates a comprehensive PRP that covers system architecture, identifies risks, and outlines specific implementation tasks with validation strategies.

The best way to plan SOC2 compliant authentication integrations is to research security best practices and official documentation to identify potential risks. This generates a detailed plan with specific implementation tasks, validation checks, and rollback strategies ensuring compliance and secure architecture.

You should avoid using a PRP for task planning when dealing with simple, low-uncertainty requests that do not require extensive web research or official documentation analysis. PRPs are designed for complex system architecture, new feature development, and integrations needing dense context and validation steps.