← Crews

Validated in Zero · Software engineering

Technical Due Diligence

Evidence-linked review of software architecture, security, dependencies, reliability, and remediation priorities.

Load

./scripts/load-crew.sh --restart ../CrewDefine/crews/technical-due-diligence

Sample prompt

Review the supplied architecture, dependency inventory, security findings, and incident history. Separate observed evidence from inference; identify material risks and produce a remediation plan with verification criteria.

Outputs

  • Decision Brief
  • Review Memo
  • Full Technical Report
  • Remediation Plan
  • Risk-Reduction Roadmap

Tools

validate information sufficiency · generate followup questions · document · knowledge base · web search · scrape website · calculator · visualizer · extract citations structured · dependency risk matrix · evidence coverage score

Roster

  • Director director — Scope control, information-sufficiency checks, and specialist coordination
  • Architecture Analyst specialist — Architecture, scalability, design constraints, and technical debt
  • Security Analyst specialist — Threat surface, vulnerability evidence, and compliance signals
  • Dependency Analyst specialist — Maintenance, vulnerability, and license-risk triage
  • Reliability Analyst specialist — SLAs, incidents, observability, and availability evidence
  • Evidence Auditor specialist — Claim-to-evidence coverage and confidence audit
  • Remediation Planner specialist — Prioritized actions, ownership, effort, and verification criteria
  • Synthesizer synthesizer — Evidence-linked technical report with explicit uncertainty

Generated by CrewDefine · validated and instantiated in Zero

Getting started Source on GitHub

Scope

The configuration evaluates supplied engineering artifacts without claiming direct repository access. It requires findings to distinguish observed evidence, inference, and missing evidence. The evidence auditor reviews claim coverage before synthesis.

Deterministic tools

dependency_risk_matrix applies transparent metadata rules to dependency records and returns the reasons for each risk tier. It does not replace authoritative vulnerability or license databases.

evidence_coverage_score reports reference coverage, unsupported high-severity findings, confidence distribution, and audit flags. Reference count is not treated as evidence quality.

Validation

The package was produced through a CrewDefine interview, passed crewdefine validate, passed Zero’s crew validator with both plugins loaded, and instantiated through Zero’s AgentRegistry as eight agents with five output modes.

Load

With CrewDefine and Zero checked out as siblings:

cd Zero
./scripts/load-crew.sh --restart ../CrewDefine/crews/technical-due-diligence