audit

Detect hallucination, overengineering, and underengineering in project artifacts.

6|1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/ferdiangunawan/rpi-stack --skill audit-ferdiangunawan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/ferdiangunawan/rpi-stack/tree/main/audit
Command: npx skills add https://github.com/ferdiangunawan/rpi-stack --skill audit-ferdiangunawan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits AI-powered artifacts (research, plan, and code) to detect hallucination, overengineering, and underengineering, enabling teams to ship higher-quality outcomes.

Core Features & Use Cases

  • Multi-dimensional quality gates: hallucination detection, overengineering risk assessment, and underengineering gaps.
  • Traceability: maps findings to PRD/requirements, dashboards, and actionable remediation steps.
  • Structured outputs: generates stakeholder-ready audit reports with clear severities and recommendations.
  • Use Case: Before releasing a feature, run an audit across PRD-aligned artifacts to identify assumptions and gaps.

Quick Start

Run the audit on a given artifact to generate a comprehensive quality report.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I detect hallucination and overengineering in AI-generated codebases?

Run an audit on your AI-generated project artifacts to identify and quantify hallucination, overengineering, and underengineering, producing a structured report mapped to your PRD for actionable remediation.

What is AI artifact auditing and when do I need it for my workflow?

AI artifact auditing is the process of applying multi-dimensional quality gates to research, plan, and code artifacts to detect hallucination and engineering gaps. You need it before releasing features to identify assumptions and trace them to requirements.

How do I trace AI codebase findings back to PRD requirements?

You trace AI codebase findings back to PRD requirements by running an audit that maps hallucination and engineering risks directly to your documented requirements, generating a management-friendly report with clear severities and recommendations.

Does the audit process work for both research and implementation artifacts?

Yes, the audit applies multi-dimensional quality gates across research, plan, and implementation artifacts, identifying gaps and assumptions while ensuring traceability to your PRD.

What is the best way to audit AI project artifacts for underengineering gaps?

The best way to audit AI project artifacts for underengineering gaps is to run a multi-dimensional quality gate assessment that identifies missing functionality, maps findings to PRD requirements, and outputs a stakeholder-ready report with actionable remediation steps.

When should I avoid using automated AI artifact audits?

You should avoid using automated AI artifact audits when you lack defined PRD requirements or baseline project artifacts, as the audit relies on traceability to requirements to accurately quantify hallucination, overengineering, and underengineering risks.