Technical Due Diligence Brief

ПродвинутыйresearchМинимальный контекст: 64K

Produces a technical due diligence brief on a vendor, product, or codebase. Covers architecture and scalability, security and compliance posture, engineering practices, dependency and licensing risk, team and bus-factor signals, and cost structure, then summarizes red flags, open questions, and a recommendation with stated confidence.

due-diligencevendor-evaluationarchitectureriskassessment

Варианты использования

  • Evaluating a SaaS vendor before a procurement decision
  • Assessing an acquisition target or open-source dependency
  • Preparing questions for a vendor technical review call
  • Summarizing technical risk for non-technical decision makers

Пример промпта

Write a technical due diligence brief.

Context: [target, available documents, intended use, decision deadline]

Return:
1. Summary and recommendation with confidence.
2. Architecture, scalability, and reliability assessment.
3. Security, compliance, and data handling.
4. Dependency, licensing, and lock-in risk.
5. Red flags and open questions to ask.

Рекомендуемые модели

claude-opus-5-5gpt-6-astragpt-6-1-sol

Совместимые инструменты

claude-codecursorkiroany

Модальности

Вход: text
→
Выход: text

Похожие Skills

competitive-intelligence-analystsecurity-questionnaire-respondercontract-analysis

Автор

OpenModels Community

@openmodelsrun