post-engine-completion-checklist

What problem does it solve?

This Skill prevents the common problem of documentation "drift" where critical details about a synth engine (like status, gallery codes, preset counts) become inaccurate shortly after completion, leading to errors and wasted time for auditors and users.

Core Features & Use Cases

• Automated Audit: Verifies and corrects factual claims in an engine's CLAUDE.md against canonical sources.
• Data Synchronization: Ensures consistency between standalone engine documentation and the central XOmnibus index.
• Knowledge Base Enrichment: Checks and populates essential knowledge compendium files (preset_design_patterns.md, architecture_patterns.md, etc.) to prevent stubs.
• Memory Management: Validates and updates MEMORY.md and associated satellite files for accurate project tracking.
• Use Case: After a synth engine build is declared complete, run this Skill to automatically audit its CLAUDE.md, update gallery codes and accent colors to match the XOmnibus master spec, verify preset counts, and ensure knowledge files are populated, preventing future documentation errors.

Quick Start

Use the post-engine-completion-checklist skill to audit the 'xoverdub' engine.