audit

Audit blueprints against six quality dimensions for gaps and inconsistencies.

3|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/wrteam-jay/blueprint --skill audit-wrteam-jay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/wrteam-jay/blueprint/tree/main/skills/blueprint/skills/audit
Command: npx skills add https://github.com/wrteam-jay/blueprint --skill audit-wrteam-jay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the need for rigorous quality control of system blueprints by systematically identifying gaps, inconsistencies, and areas for improvement across defined dimensions.

Core Features & Use Cases

  • Comprehensive Auditing: Evaluates blueprints against six critical dimensions: Terminology consistency, Scenario coverage, Domain model completeness, Requirements quality, Decision log and open questions, and Implementation leakage.
  • Gap Identification: Pinpoints missing flows, terminology conflicts, untestable requirements, and implementation details that should not be in a blueprint.
  • Use Case: Before a major feature release, use the audit skill to ensure the blueprint is clear, complete, and accurately reflects the intended system behavior, preventing misunderstandings and technical debt.

Quick Start

Run a systematic checklist audit of the blueprint located in the current directory.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I audit a system blueprint for missing flows and untestable requirements?

To audit a system blueprint, you run a systematic checklist against six quality dimensions to identify missing flows, terminology conflicts, and untestable requirements. This evaluates scenario coverage, domain model completeness, and requirements quality.

What is implementation leakage in a system specification and how do I find it?

Implementation leakage in a system specification is the inclusion of technical implementation details where only conceptual behavior should exist. You find it by auditing the blueprint against defined quality dimensions to isolate inappropriate technical decisions from system behavior.

When do I need to run a requirements review on my system specification?

You need to run a requirements review on your system specification before a major feature release to ensure clarity, completeness, and accurate system behavior representation. This prevents misunderstandings and technical debt by identifying gaps and terminology conflicts early.

Can I check terminology consistency across my entire domain model?

Yes, you can check terminology consistency across your domain model by conducting a systematic audit. The audit evaluates terminology conflicts and domain model completeness to ensure uniform language usage throughout the blueprint.

What are the limitations of a manual documentation review for quality assurance?

A manual documentation review for quality assurance often lacks the rigor to systematically evaluate all six dimensions, missing subtle implementation leakage or untestable requirements. A systematic audit enforces defined severity guidelines to standardize finding gaps and conflicts.

Does the blueprint audit require any specific dependencies or environment setup?

No specific dependencies or environment setup are required. You can run the systematic blueprint quality assurance audit directly against the existing system specification to identify missing flows and domain model gaps.