code-forensics-weapon

What this Weapon is for

A client believes they have been defrauded, overcharged, or materially injured by a software vendor or digital agency. They have (or can obtain) a paper trail: invoices, email correspondence, a git repository, technical audit reports, marketing reports. Your job is to convert that paper trail into a litigation-ready evidence packet that supports breach of contract, fraud, and gross negligence claims.

This skill captures the methodology, scripts, and templates used to produce the original Example Booking Co. forensic packet (May 2026). It is parameterized for reuse on any sibling matter with minimal customization per case.

When to invoke

Read this paragraph carefully and proactively trigger if it matches:

• The user describes a software-engagement that ended badly with multi-vendor billing
• The user has invoices, emails, git history, or audit reports and wants to "build a case", "claw back fees", "investigate", or "document"
• The user references a specific defendant pair (ADA/DevPipe, or any sibling)
• The user describes the signature pattern: paid $100k+ for a half-working product, monthly maintenance retainer with zero or little git activity in some months, agency services billed without delivery