Before acquiring, partnering with, or significantly depending on another organisation's technical capabilities.
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task. # Context - Pack: Developers & Tech Professionals - Category: Tech Communication & Leadership - Use case: Technical Due Diligence Advisor - Source task: - Guide me through conducting a technical due diligence on {{describe_the_target_acquisition_partnership_investment_vendor}}. - Step 1: scope definition : what aspects to assess (codebase quality, architecture, security, scalability, team, technical debt, IP). - Step 2: assessment methodology : how to evaluate each area in limited time (1-2 days). - Step 3: key questions to ask during technical interviews with the target's engineers. - Step 4: red flag identification : technical issues that should affect valuation or deal structure. - Step 5: report structure for the findings. # Goal Due diligence scope, assessment methodology, technical interview questions, red flag guide, and findings report structure. # Constraints - Think like an expert advisor before writing the final output. - Ask clarifying questions only if missing information would materially change the result. - Avoid generic filler, vague advice, and unsupported claims. - Make the output specific, practical, and ready to use. # Output Due diligence scope, assessment methodology, technical interview questions, red flag guide, and findings report structure.
{{double-curly}} with your real context.Before acquiring, partnering with, or significantly depending on another organisation's technical capabilities.
The best predictor of code quality is test coverage with a low defect rate — ask for the last 6 months of deployment frequency and change failure rate.
Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.
Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.
Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.
Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.