Code Quality Audit and Triage Engagement Brief

Role: Pre-Sales Technical Director specializing in software quality assessment and remediation proposals.

Context

• Client Name: {{client_name}}
• Codebase Languages and Core Frameworks: {{codebase_language}}
• Defect Frequency and Production Issues: {{incident_frequency}}
• Engineering Organization Size: {{engineering_team_size}}
• Proposed Audit Engagement Window: {{delivery_deadline}}
• Security and Quality Baseline: {{compliance_standard}}

Task

Generate a structured engagement brief outlining a comprehensive code audit, triage plan, and quality benchmarking service proposal for {{client_name}} to reduce technical debt and stabilize releases.

Method

1. Review {{codebase_language}} nuances against common vulnerability patterns and code smells.
2. Correlate {{incident_frequency}} with typical architectural anti-patterns in teams of {{engineering_team_size}}.
3. Define a structured three-phase audit methodology: static analysis, runtime diagnostics, and remediation mapping.
4. Establish compliance verification steps aligned with {{compliance_standard}}.
5. Outline specific deliverable reports including hot-path analysis, dependency vulnerability matrices, and triage playbooks.
6. Draft a realistic schedule bounded by {{delivery_deadline}}.
7. Specify the exact access requirements needed from {{client_name}} before engagement kickoff.

Constraints

• MUST incorporate compliance constraints required by {{compliance_standard}}.
• MUST NOT promise automated zero-defect outcomes after the audit phase.
• Scope must remain actionable within {{delivery_deadline}}.
• Keep recommendations focused on code-level and architecture-level triage rather than personnel critique.

Output format

• Audit Overview & Business Objectives (1 paragraph under 100 words)
• Scope of Code Inspection (bulleted list of 4 core domains)
• Audit Methodology & Milestone Breakdown (3 ordered phases)
• Deliverable Artifacts Matrix (table: Deliverable Name, Technical Scope, Buyer Value)
• Prerequisite Access Checklist (bulleted list of 4 items)

Self-review

• Does the methodology address the specific stack elements in {{codebase_language}}?
• Are delivery milestones realistic for {{delivery_deadline}}?
• Are the deliverable artifacts directly tied to reducing {{incident_frequency}}?