app-audit

Audit the Gait OSS project and output a go/no-go report with P0-P3 blockers.

12|5|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/davidahmann/gait --skill app-audit-davidahmann
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: app-audit
Source: https://github.com/davidahmann/gait/tree/main/.agents/skills/app-audit
Command: npx skills add https://github.com/davidahmann/gait --skill app-audit-davidahmann

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for a rigorous, evidence-based audit of the Gait OSS project to ensure its readiness for product launch, covering critical aspects like architecture, security, and go-to-market strategy.

Core Features & Use Cases

  • Comprehensive Readiness Assessment: Evaluates product, architecture, DX, security, and GTM readiness.
  • Evidence-Based Reporting: Generates a strict go/no-go report with P0-P3 blockers and launch risks, citing command output and file paths.
  • Use Case: Before a major release, use this Skill to perform a final audit, identifying any critical blockers or risks that could jeopardize the launch's success.

Quick Start

Use the app-audit skill to run a full MVP readiness audit and return a strict blocker-ranked verdict.

Frequently Asked Questions about app-audit

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

FAQPage Schema
How do I audit open source project readiness before a product launch?▼

An open source project readiness audit evaluates architecture, security, developer experience, and go-to-market strategy to produce a strict go/no-go report. It identifies P0-P3 blockers and launch risks by technology, messaging, and expectations using command output and file path evidence.

How do I run a go-to-market readiness assessment for an OSS project?▼

Running a go-to-market readiness assessment requires executing CLI commands for diagnostics and artifact inspection across the project. This produces a strict go/no-go report with P0-P3 blockers and launch risk assessments by technology, messaging, and expectations.

Does the readiness audit require any specific environment setup or CLI tools?▼

Yes, the readiness audit requires executing Gait CLI commands for diagnostics and artifact inspection. This CLI execution gathers the evidence required to generate the strict go/no-go report with P0-P3 blockers and launch risk assessments.

What is the best way to identify P0-P3 blockers before a major release?▼

The best way to identify P0-P3 blockers before a major release is to perform an evidence-based audit across product, architecture, developer experience, security, and go-to-market readiness. This generates a strict go/no-go report citing command output and file paths.

Why does my open source launch fail despite passing basic security audits?▼

Your open source launch might fail because basic security audits do not evaluate architecture, developer experience, or go-to-market readiness. A comprehensive evidence-based audit is needed to identify P0-P3 blockers across messaging, technology, and expectations.