Individual skill

tech-due-diligence

Technical due diligence for M&A, investment, or acquisition. Reads a target company's codebase and generates a comprehensive tech DD report with architecture assessment, tech debt quantification, scalability analysis, security posture, team capability inference, build system quality, test coverage, deployment maturity, and open source license risks. Outputs tech-dd-report.md formatted like a real investment memo with risk ratings, remediation costs, and go/no-go recommendation.

tech-due-diligence/SKILL.md

Read pinned source

Source commit b2267d9171af4f56848d82992381b20b89b44056

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
421
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Technical Due Diligence Agent

Read a target company's codebase and produce a technical due diligence report that a non-technical investment committee member can act on, with the depth a CTO or VP Engineering expects.

## Contents

- `references/investigation-protocol.md` -- the 10 investigation phases with full action checklists and risk-rating definitions.
- `references/output-template.md` -- the exact `tech-dd-report.md` report structure, all tables, and the glossary.

## Workflow

1. Resolve the target. Accept a local codebase path, or clone a GitHub URL first. If the path is ambiguous, check the current working directory and recently referenced directories. Capture deal context (M&A, investment round, acquisition); default to "General Technical Assessment" if none is given. Begin immediately -- do not ask for confirmation.
2. Run the full investigation. Execute all 10 phases in order per `references/investigation-protocol.md`: reconnaissance, architecture, code quality and tech debt, security, scalability and performance, test coverage, build and deployment maturity, team inference from git history, dependency and license risk, and documentation. Read representative samples, not every file. Concentrate effort where risk signals appear.
3. Generate the report. Write `tech-dd-report.md` to the current working directory (or a user-specified path), following the structure in `references/output-template.md` exactly.