playbook-audit

Audit RDPI playbook documentation against the current repository state.

Updated Aug 27, 2026

Search Tags:#playbook #health check #CLAUDE.md #repository audit #documentation freshness #artifact cleanup #RDPI workflow

Ready to run

npx skills add https://github.com/KMakayee/playbook --skill playbook-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: playbook-audit
Source: https://github.com/KMakayee/playbook/tree/main/.claude/skills/playbook-audit
Command: npx skills add https://github.com/KMakayee/playbook --skill playbook-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents the RDPI playbook from silently drifting out of sync with the actual repository structure and conventions.

Core Features & Use Cases

Checks CLAUDE.md freshness: Compares key CLAUDE.md sections (overview, architecture, conventions, testing, commands, paths, dependencies) against the current codebase state and flags placeholder markers or stale instructions.
Cleans up old artifacts: Detects leftover files in tasks/ from previous sessions and lets you delete or keep them.
Generates a structured audit report: Writes tasks/audit-report.md using the template when available, otherwise creates a default structure.
Use case: When you update dependencies, reorganize directories, or change workflows, run this audit to verify the playbook documentation and operational artifacts remain accurate.

Quick Start

Run the playbook audit command: /playbook-audit.

Frequently Asked Questions about playbook-audit

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

FAQPage Schema

How do I check if CLAUDE.md documentation has drifted out of sync with my repository?▼

To check CLAUDE.md freshness, compare its overview, architecture, conventions, testing, commands, paths, and dependencies sections against the current codebase state to flag placeholder markers or stale instructions. The audit reads CLAUDE.md and uses an Explore subagent to cross-reference sections with the repository.

What is the best way to clean up leftover task artifacts from previous development sessions?▼

The best way to clean up leftover artifacts is to scan the tasks/ directory for files from previous sessions and selectively delete or keep them. This prevents stale artifacts from accumulating and confusing the repository state during maintenance.

How do I generate a structured audit report for my repository playbook?▼

To generate a structured audit report, write tasks/audit-report.md using an available template or a default fallback structure. This report captures the results of the playbook freshness check and artifact cleanup for periodic repository maintenance.

When should I run a repository documentation health check?▼

You should run a repository documentation health check when you update dependencies, reorganize directories, or change workflows. This verifies that playbook documentation and operational artifacts remain accurate against the current codebase state.

Does the playbook audit work without any external dependencies?▼

Yes, the playbook audit works without external dependencies. It requires only reading CLAUDE.md and tasks/ directories, comparing sections to the codebase with an Explore subagent, and optionally proposing edits to generate the audit report.