audit-enhancements

Audit code, product, UX, content, and infrastructure to generate TDMS-ready findings.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/jasonmichaelbell78-creator/framework --skill audit-enhancements
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-enhancements
Source: https://github.com/jasonmichaelbell78-creator/framework/tree/main/.claude/skills/audit-enhancements
Command: npx skills add https://github.com/jasonmichaelbell78-creator/framework --skill audit-enhancements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auditors and teams struggle to identify and fix across-codebase issues spanning code, product, UX, content, and processes; this skill provides a structured, transparent workflow to surface and document holistic improvements.

Core Features & Use Cases

  • Multi-domain audit across code, product, UX, content, workflows, infrastructure, external services, and meta-tooling
  • TDMS integration for debt creation and tracking
  • Built-in honesty guardrails requiring counterarguments for every finding
  • Phase-based process: Broad Scan, Deep Dive (opt-in), and Synthesis
  • Generates a consolidated enhancement report and TDMS intake

Quick Start

Run the enhancement audit workflow for the current project to generate TDMS-ready insights.

Frequently Asked Questions about audit-enhancements

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a comprehensive enhancement audit across my codebase and product?▼

You can automate a comprehensive enhancement audit by running a phase-based workflow that scans code, product, UX, content, and infrastructure to surface holistic improvements for review. It generates a consolidated report and TDMS intake.

What is a holistic enhancement audit and when do I need it?▼

A holistic enhancement audit identifies cross-domain issues spanning code, product, UX, content, and processes. You need it when teams struggle to surface and document project-wide technical debt and quality improvements transparently.

How do I generate TDMS-ready findings for technical debt tracking?▼

To generate TDMS-ready findings, execute the audit workflow which integrates directly with the TDMS intake system. It produces traceable debt creation entries from multi-domain scans for your technical debt management.

Can I audit external services and infrastructure as part of my project quality assurance?▼

Yes, you can audit external services and infrastructure alongside code, product, UX, and workflows. The audit applies to the entire project scope, performing a broad scan followed by an opt-in deep dive for comprehensive coverage.

Does the enhancement audit workflow enforce any quality guardrails for findings?▼

Yes, the audit enforces mandatory counterarguments for every finding as built-in honesty guardrails. This ensures transparent, validated results during the synthesis phase before generating the final TDMS-ready enhancement report.

What's the best way to document cross-codebase technical debt for review?▼

The best way to document cross-codebase technical debt is using an automated phase-based audit that produces TDMS-ready findings. It transitions from a broad scan to synthesis, outputting a consolidated enhancement report for stakeholder review.