audit

Audit PRD requirements against specs, code, and tests to produce a compliance report.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/yoshisada/ai-repo-template --skill audit-yoshisada
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/yoshisada/ai-repo-template/tree/main/plugin-kiln/skills/audit
Command: npx skills add https://github.com/yoshisada/ai-repo-template --skill audit-yoshisada

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams enforce PRD-to-spec and spec-to-code alignment by systematically auditing current implementations to identify gaps, inconsistencies, and blockers.

Core Features & Use Cases

  • Phase-driven PRD audit that gathers PRD requirements, governing principles, and specs, then maps coverage to FRs.
  • Detects uncovered PRD requirements, creates new FRs, updates tasks, and documents blockers when gaps cannot be resolved.
  • Produces a final compliance report highlighting pass/fail status and blockers for stakeholder review.

Quick Start

Initiate a PRD compliance audit against the current implementation and review results for gaps and blockers.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I audit PRD compliance against current code and tests?

PRD compliance auditing identifies gaps between requirements and implementation by mapping specs, code, and tests to functional requirements. It iteratively applies multi-phase processes to fix uncovered requirements or document blockers.

What is the best way to ensure spec-to-code alignment for product requirements?

Spec-to-code alignment is enforced by auditing current implementations against governing principles and specs. The process detects uncovered PRD requirements, creates new FRs, updates tasks, and flags unresolved gaps as blockers.

How do I document blockers when PRD requirements are not implemented?

Blockers are documented during the audit when gaps between PRD requirements and code cannot be resolved. The process records these unresolved issues alongside pass/fail statuses in a final compliance report for stakeholder review.

What does a PRD compliance report include for stakeholder review?

A PRD compliance report highlights pass/fail statuses and documents all blockers found during the end-to-end audit. It maps functional requirements coverage to show stakeholders exactly where implementation gaps exist.

Can I automate functional requirements mapping from PRD to test coverage?

Functional requirements mapping is automated by auditing PRD requirements, governing principles, and specs against current tests. The process adds missing FRs, aligns tests, and annotates code to close implementation gaps.

Do I need existing specs and tests before starting a PRD audit?

Existing specs, code, and tests are required inputs for a PRD audit. The auditing process evaluates these current implementations against PRD requirements to identify inconsistencies, generate missing FRs, and document blockers.